> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Morten Brørup
> Sent: Thursday, 27 May 2021 20.15
>
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
> > Sent: Thursday, 27 May 2021 19.22
> >
> > On Thu, May 27, 2021 at 10:39:59PM +0530, Manish Sharma wrote:
> > >
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Thursday, 27 May 2021 19.22
>
> On Thu, May 27, 2021 at 10:39:59PM +0530, Manish Sharma wrote:
> >For the case I have, hardly 2% of the data buffers which are being
> >copied get looked at - mostly its for DMA.
On Thu, May 27, 2021 at 10:39:59PM +0530, Manish Sharma wrote:
>For the case I have, hardly 2% of the data buffers which are being
>copied get looked at - mostly its for DMA. Having a version of DPDK
>memcopy that does non temporal copies would definitely be good.
>If in my case, I
For the case I have, hardly 2% of the data buffers which are being copied
get looked at - mostly its for DMA. Having a version of DPDK memcopy that
does non temporal copies would definitely be good.
If in my case, I have a lot of CPUs doing the copy in parallel, would I/OAT
driver copy accelerator
On Thu, May 27, 2021 at 05:49:19PM +0200, Morten Brørup wrote:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
> > Sent: Tuesday, 25 May 2021 11.20
> >
> > On Mon, May 24, 2021 at 11:43:24PM +0530, Manish Sharma wrote:
> > > I am looking at the source for rte_memcpy (this
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Tuesday, 25 May 2021 11.20
>
> On Mon, May 24, 2021 at 11:43:24PM +0530, Manish Sharma wrote:
> > I am looking at the source for rte_memcpy (this is a discussion only
> > for x86-64)
> >
> > For one of the cases, when
On Mon, May 24, 2021 at 11:43:24PM +0530, Manish Sharma wrote:
> I am looking at the source for rte_memcpy (this is a discussion only for
> x86-64)
>
> For one of the cases, when aligned correctly, it uses
>
> /**
> * Copy 64 bytes from one location to another,
> * locations should not overlap.
I am looking at the source for rte_memcpy (this is a discussion only for
x86-64)
For one of the cases, when aligned correctly, it uses
/**
* Copy 64 bytes from one location to another,
* locations should not overlap.
*/
static __rte_always_inline void
rte_mov64(uint8_t *dst, const uint8_t *src
8 matches
Mail list logo
