From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Shai Brandes <shaibran@amazon.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
Ron Beider <rbeider@amazon.com>,
Amit Bernstein <amitbern@amazon.com>,
Wajeeh Atrash <atrwajee@amazon.com>,
Igor Chauskin <igorch@amazon.com>,
Michal Krawczyk <mk@semihalf.com>, Artur Rojek <ar@semihalf.com>
Subject: Re: [PATCH] net/ena: revert redefining memcpy
Date: Sun, 22 Sep 2024 05:08:03 +0100 [thread overview]
Message-ID: <ce049d57-f970-4258-8585-72a55d10f3c2@amd.com> (raw)
In-Reply-To: <20240912051243.GC6879@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On 9/12/2024 6:12 AM, Tyler Retzlaff wrote:
> On Mon, Aug 12, 2024 at 08:34:17AM -0700, Stephen Hemminger wrote:
>> Redefining memcpy as rte_memcpy has no performance gain on
>> current compilers, and introduced bugs like this one where
>> rte_memcpy() will be detected as referencing past the destination.
>>
>> Bugzilla ID: 1510
>> Fixes: 142778b3702a ("net/ena: switch memcpy to optimized version")
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>> ---
>
> Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
>
Acked-by: Shai Brandes <shaibran@amazon.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-09-22 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200~bug-1510-3@http.bugs.dpdk.org>
2024-08-12 15:34 ` Stephen Hemminger
2024-08-12 20:53 ` Wathsala Wathawana Vithanage
2024-08-13 8:57 ` Morten Brørup
2024-09-12 5:12 ` Tyler Retzlaff
2024-09-12 8:19 ` Ferruh Yigit
2024-09-12 14:53 ` Brandes, Shai
2024-09-16 6:33 ` Brandes, Shai
2024-09-16 15:11 ` Stephen Hemminger
2024-09-16 16:06 ` Brandes, Shai
2024-09-22 4:08 ` Ferruh Yigit [this message]
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=ce049d57-f970-4258-8585-72a55d10f3c2@amd.com \
--to=ferruh.yigit@amd.com \
--cc=amitbern@amazon.com \
--cc=ar@semihalf.com \
--cc=atrwajee@amazon.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=rbeider@amazon.com \
--cc=roretzla@linux.microsoft.com \
--cc=shaibran@amazon.com \
--cc=stephen@networkplumber.org \
/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).