From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org,
"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
"Vipin Varghese" <vipin.varghese@amd.com>
Subject: Re: [PATCH v2] eal/x86: optimize memcpy of small sizes
Date: Fri, 21 Nov 2025 09:11:59 -0800 [thread overview]
Message-ID: <20251121091159.4783d97b@phoenix.local> (raw)
In-Reply-To: <aSCbGWNQ7dr7EE7A@bricha3-mobl1.ger.corp.intel.com>
On Fri, 21 Nov 2025 17:02:17 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:
> > As I have said before would rather that DPDK move away from having its
> > own specialized memcpy. How is this compared to stock inline gcc?
> > The main motivation is that the glibc/gcc team does more testing across
> > multiple architectures and has a community with more expertise on CPU
> > special cases.
>
> I would tend to agree. Even if we get rte_memcpy a few cycles faster, I
> suspect many apps wouldn't notice the difference. However, I understand
> that the virtio/vhost libraries gain from using rte_memcpy over standard
> memcpy - or at least used to. Perhaps we can consider deprecating
> rte_memcpy and just putting a vhost-specific memcpy in that library?
It would be good to figure out why vhost is better with rte_memcpy,
maybe there is some alignment assumption that is in one and not the other?
next prev parent reply other threads:[~2025-11-21 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 11:45 [PATCH] eal/x86: reduce memcpy code duplication Morten Brørup
2025-11-21 10:35 ` [PATCH v2] eal/x86: optimize memcpy of small sizes Morten Brørup
2025-11-21 16:57 ` Stephen Hemminger
2025-11-21 17:02 ` Bruce Richardson
2025-11-21 17:11 ` Stephen Hemminger [this message]
2025-11-21 21:36 ` Morten Brørup
2025-11-21 10:40 ` Morten Brørup
2025-11-21 10:40 ` [PATCH v3] " 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=20251121091159.4783d97b@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mb@smartsharesystems.com \
--cc=vipin.varghese@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).