From: Stephen Hemminger <stephen@networkplumber.org>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: olivier.matz@6wind.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mbuf: replace c memcpy() code semantics with optimized rte_memcpy()
Date: Thu, 23 Jul 2020 08:47:15 -0700 [thread overview]
Message-ID: <20200723084715.1f055aff@hermes.lan> (raw)
In-Reply-To: <20200723070240.14749-1-sarosh.arif@emumba.com>
On Thu, 23 Jul 2020 12:02:40 +0500
Sarosh Arif <sarosh.arif@emumba.com> wrote:
> Since rte_memcpy is more optimized it should be used instead of memcpy
>
> Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
Really did you measure this.
For fixed size structures, compiler can inline memcpy small set of instructions.
next prev parent reply other threads:[~2020-07-23 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 7:02 Sarosh Arif
2020-07-23 15:47 ` Stephen Hemminger [this message]
2020-07-28 13:30 ` Sarosh Arif
2020-07-28 13:50 ` Olivier Matz
2020-07-28 17:46 ` Stephen Hemminger
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=20200723084715.1f055aff@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=sarosh.arif@emumba.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).