From: David Marchand <david.marchand@redhat.com>
To: Leyi Rong <leyi.rong@intel.com>
Cc: mb@smartsharesystems.com, bruce.richardson@intel.com, dev@dpdk.org
Subject: Re: [PATCH] eal/x86: remove redundant round to improve performance
Date: Tue, 4 Apr 2023 15:15:46 +0200 [thread overview]
Message-ID: <CAJFAV8z2CyR2jRBvqD=7b36TcDFa7HcB3-DCVSJJ27EvahW7qA@mail.gmail.com> (raw)
In-Reply-To: <20230329091658.1599349-1-leyi.rong@intel.com>
On Wed, Mar 29, 2023 at 11:17 AM Leyi Rong <leyi.rong@intel.com> wrote:
>
> In rte_memcpy_aligned(), one redundant round is taken in the 64 bytes
> block copy loops if the size is a multiple of 64. So, let the catch-up
> copy the last 64 bytes in this case.
Fixes: f5472703c0bd ("eal: optimize aligned memcpy on x86")
>
> Suggested-by: Morten Brørup <mb@smartsharesystems.com>
> Signed-off-by: Leyi Rong <leyi.rong@intel.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2023-04-04 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 9:16 Leyi Rong
2023-03-29 9:30 ` Morten Brørup
2023-03-29 10:20 ` Bruce Richardson
2023-04-04 13:15 ` David Marchand [this message]
2023-06-07 16:44 ` David Marchand
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='CAJFAV8z2CyR2jRBvqD=7b36TcDFa7HcB3-DCVSJJ27EvahW7qA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=leyi.rong@intel.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 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).