All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Manish Sharma <manish.sharmajee75@gmail.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] rte_memcpy - fence and stream
Date: Thu, 27 May 2021 18:22:28 +0100	[thread overview]
Message-ID: <YK/VVIlCwQ8cHwB3@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAOT2AHVrMkq=6nw-YLu+Bq34w-u4LJARSmoRgjia4m5DR3g0LA@mail.gmail.com>

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 have a lot of CPUs doing the copy in parallel, would
>    I/OAT driver copy accelerator still help?
> 
It will depend upon the size of the copies being done. For bigger packets
the accelerator can help free up CPU cycles for other things.

However, if only 2% of the data which is being copied gets looked at, why
does it need to be copied? Can the original buffers not be used in that
case?

Regards,
/Bruce

  reply	other threads:[~2021-05-27 17:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24  8:49 [dpdk-dev] rte_memcpy Manish Sharma
2021-05-24 18:13 ` [dpdk-dev] rte_memcpy - fence and stream Manish Sharma
2021-05-25  9:20   ` Bruce Richardson
2021-05-27 15:49     ` Morten Brørup
2021-05-27 16:25       ` Bruce Richardson
2021-05-27 17:09         ` Manish Sharma
2021-05-27 17:22           ` Bruce Richardson [this message]
2021-05-27 18:15             ` Morten Brørup
2021-06-22 21:55               ` Morten Brørup

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YK/VVIlCwQ8cHwB3@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=manish.sharmajee75@gmail.com \
    --cc=mb@smartsharesystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.