From: Liangxing Wang <wangliangxing@hygon.cn>
To: "Varghese, Vipin" <Vipin.Varghese@amd.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"P, Thiyagarajan" <Thiyagarajan.P@amd.com>,
"Murali Krishna, Bala" <Bala.MuraliKrishna@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: RE: [PATCH v6] eal/x86: optimize memcpy of small sizes
Date: Thu, 22 Jan 2026 07:28:52 +0000 [thread overview]
Message-ID: <9ac18b2e8f684bb5a9fa91815bf46a49@hygon.cn> (raw)
In-Reply-To: <PH7PR12MB85961D3A7388DF0C0445915A8297A@PH7PR12MB8596.namprd12.prod.outlook.com>
Hi @ Varghese, Vipin,
I am interested in this rte_memcpy patch performance on our x86 platform too. May you please share the configuration file and steps for your dma-perf test then I can run the same on our platform? Thanks.
Regards,
Liangxing
> -----Original Message-----
> From: Varghese, Vipin <Vipin.Varghese@amd.com>
> Sent: 2026年1月22日 15:00
> To: Varghese, Vipin <Vipin.Varghese@amd.com>; Morten Brørup
> <mb@smartsharesystems.com>; Stephen Hemminger
> <stephen@networkplumber.org>; P, Thiyagarajan <Thiyagarajan.P@amd.com>;
> Murali Krishna, Bala <Bala.MuraliKrishna@amd.com>
> Cc: dev@dpdk.org; Bruce Richardson <bruce.richardson@intel.com>;
> Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
> Subject: RE: [PATCH v6] eal/x86: optimize memcpy of small sizes
>
> [Public]
>
> Hi @Morten Brørup,
>
> We (@P, Thiyagarajan @Murali Krishna, Bala and myself) have used dma-perf
> to validate the performance from 1B to 17B payload.
> Following are our observations
>
> With c_args `-DRTE_MEMCPY_AVX512` enabled on zen4, we observe around
> 25% performance regression for payload size 1B to 15B and 17B.
> While in case of 16B we see improvement in Mops by 40%.
>
> Without c_args `-DRTE_MEMCPY_AVX512` enabled on zen4, we observe +-4%
> variation from 1B to 17B.
>
> `We are investigating the variation is more prominent with avx512 memcpy.`
>
> Note:
> 1. in zen4 ld|str is broken to 32B. While in zen5 ld|str is 64B.
> 2. we tested memif copy on zen5 with patch (without -DRTE_MEMCPY_AVX512)
> on 64B and 65B payload. It is same as zen4 observation (shared in previous
> email).
>
>
>
> > -----Original Message-----
> > From: Varghese, Vipin <Vipin.Varghese@amd.com>
> > Sent: Wednesday, January 21, 2026 5:19 PM
> > To: Morten Brørup <mb@smartsharesystems.com>; Stephen Hemminger
> > <stephen@networkplumber.org>
> > Cc: dev@dpdk.org; Bruce Richardson <bruce.richardson@intel.com>;
> > Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
> > Subject: RE: [PATCH v6] eal/x86: optimize memcpy of small sizes
> >
> > Caution: This message originated from an External Source. Use proper
> > caution when opening attachments, clicking links, or responding.
> >
> >
> > [Public]
> >
> > Hi @Morten Brørup, please find our observation running testpmd with
> > memif in zero-copy mode disabled (rte_memcpy enabled).
> >
> > 1. DPDK baseline version: 25.11 we tested with testpmd in io & flowgen
> mode 2.
> > using no cargs for memcpy (rtemov32) and with patch 64B & 65B we get
> > `15.5Mpps` 3. using cargs ` -DRTE_MEMCPY_AVX512` for memcpy
> (rtemov64)
> > and with patch 64B & 65B we get `14.8Mpps`
> >
> > We will run with dma-perf application for payload sizes of
> > 1,2,3,4,5,...etc
> >
> > Regards
> > Vipin Varghese
next prev parent reply other threads:[~2026-01-22 7:29 UTC|newest]
Thread overview: 43+ 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
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
2025-11-24 13:36 ` Morten Brørup
2025-11-24 15:46 ` Patrick Robb
2025-11-28 14:02 ` Konstantin Ananyev
2025-11-28 15:55 ` Morten Brørup
2025-11-28 18:10 ` Konstantin Ananyev
2025-11-29 2:17 ` Morten Brørup
2025-12-01 9:35 ` Konstantin Ananyev
2025-12-01 10:41 ` Morten Brørup
2025-11-24 20:31 ` [PATCH v4] " Morten Brørup
2025-11-25 8:19 ` Morten Brørup
2025-12-01 15:55 ` [PATCH v5] " Morten Brørup
2025-12-03 13:29 ` Morten Brørup
2026-01-03 17:53 ` Morten Brørup
2026-01-09 15:05 ` Varghese, Vipin
2026-01-11 15:52 ` Konstantin Ananyev
2026-01-11 16:01 ` Stephen Hemminger
2026-01-12 8:02 ` Morten Brørup
2026-01-12 16:00 ` Scott Mitchell
2026-01-13 0:39 ` Stephen Hemminger
2026-01-12 12:03 ` [PATCH v6] " Morten Brørup
2026-01-13 23:19 ` Stephen Hemminger
2026-01-20 11:00 ` Varghese, Vipin
2026-01-20 11:19 ` Varghese, Vipin
2026-01-20 11:22 ` Morten Brørup
2026-01-21 11:48 ` Varghese, Vipin
2026-01-22 6:59 ` Varghese, Vipin
2026-01-22 7:28 ` Liangxing Wang [this message]
2026-01-23 6:58 ` Varghese, Vipin
2026-02-20 11:08 ` [PATCH v7] " Morten Brørup
2026-03-11 7:28 ` Morten Brørup
2026-03-11 16:58 ` Bruce Richardson
2026-03-11 18:29 ` Morten Brørup
2026-03-11 19:09 ` Bruce Richardson
2026-03-12 8:33 ` Konstantin Ananyev
2026-03-19 15: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=9ac18b2e8f684bb5a9fa91815bf46a49@hygon.cn \
--to=wangliangxing@hygon.cn \
--cc=Bala.MuraliKrishna@amd.com \
--cc=Thiyagarajan.P@amd.com \
--cc=Vipin.Varghese@amd.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=mb@smartsharesystems.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