DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
To: fengchengwen <fengchengwen@huawei.com>,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	"david.hunt@intel.com" <david.hunt@intel.com>,
	"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
	Akhil Goyal <gakhil@marvell.com>,
	"cristian.dumitrescu@intel.com" <cristian.dumitrescu@intel.com>,
	"Yigit, Ferruh" <Ferruh.Yigit@amd.com>,
	"konstantin.ananyev@huawei.com" <konstantin.ananyev@huawei.com>,
	"mb@smartsharesystems.com" <mb@smartsharesystems.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"haijie1@huawei.com" <haijie1@huawei.com>,
	 "stable@dpdk.org" <stable@dpdk.org>,
	"Ande, Venkat Kumar" <VenkatKumar.Ande@amd.com>,
	Dengdui Huang <huangdengdui@huawei.com>
Subject: Re: [EXTERNAL] [PATCH v2] examples/l3fwd: adjust Tx burst size based on Rx burst
Date: Sat, 1 Nov 2025 12:53:36 +0000	[thread overview]
Message-ID: <CH3PR12MB8233D6BB749461012556FD4986F9A@CH3PR12MB8233.namprd12.prod.outlook.com> (raw)
In-Reply-To: <81d70c4e-aa4b-482e-a708-be477ed22f5b@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 3838 bytes --]

[AMD Official Use Only - AMD Internal Distribution Only]

Hi Fengchengwen,

I will send the v3 patch early next week.

Thanks & Regards,
Sivaprasad

________________________________
From: fengchengwen <fengchengwen@huawei.com>
Sent: Friday, October 31, 2025 2:48 PM
To: Tummala, Sivaprasad <Sivaprasad.Tummala@amd.com>; Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; david.hunt@intel.com <david.hunt@intel.com>; anatoly.burakov@intel.com <anatoly.burakov@intel.com>; Jerin Jacob <jerinj@marvell.com>; radu.nicolau@intel.com <radu.nicolau@intel.com>; Akhil Goyal <gakhil@marvell.com>; cristian.dumitrescu@intel.com <cristian.dumitrescu@intel.com>; Yigit, Ferruh <Ferruh.Yigit@amd.com>; konstantin.ananyev@huawei.com <konstantin.ananyev@huawei.com>; mb@smartsharesystems.com <mb@smartsharesystems.com>
Cc: dev@dpdk.org <dev@dpdk.org>; haijie1@huawei.com <haijie1@huawei.com>; stable@dpdk.org <stable@dpdk.org>; Ande, Venkat Kumar <VenkatKumar.Ande@amd.com>; Dengdui Huang <huangdengdui@huawei.com>
Subject: Re: [EXTERNAL] [PATCH v2] examples/l3fwd: adjust Tx burst size based on Rx burst

Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.


Hi Sivaprasad,

Are you going to send v3 (add log) version?

There is another patch about adjust burst size [1], if this patch
don't continue, maybe we should restart that one.

[1] https://patchwork.dpdk.org/project/dpdk/patch/20241204020622.977156-1-haijie1@huawei.com/

Thanks

On 10/9/2025 10:32 AM, Tummala, Sivaprasad wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Pavan,
>
> Please find my response inline.
>
> ________________________________
> From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
> Sent: Tuesday, June 10, 2025 7:59 PM
> To: Tummala, Sivaprasad <Sivaprasad.Tummala@amd.com>; david.hunt@intel.com <david.hunt@intel.com>; anatoly.burakov@intel.com <anatoly.burakov@intel.com>; Jerin Jacob <jerinj@marvell.com>; radu.nicolau@intel.com <radu.nicolau@intel.com>; Akhil Goyal <gakhil@marvell.com>; cristian.dumitrescu@intel.com <cristian.dumitrescu@intel.com>; Yigit, Ferruh <Ferruh.Yigit@amd.com>; konstantin.ananyev@huawei.com <konstantin.ananyev@huawei.com>; mb@smartsharesystems.com <mb@smartsharesystems.com>
> Cc: dev@dpdk.org <dev@dpdk.org>; haijie1@huawei.com <haijie1@huawei.com>; stable@dpdk.org <stable@dpdk.org>; Ande, Venkat Kumar <VenkatKumar.Ande@amd.com>; Dengdui Huang <huangdengdui@huawei.com>
> Subject: Re: [EXTERNAL] [PATCH v2] examples/l3fwd: adjust Tx burst size based on Rx burst
>
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
>>> Previously, the TX burst size was fixed at 256, leading to performance
>>> degradation in certain scenarios.
>>>
>>> This patch introduces logic to set the TX burst size to match the
>>> configured RX burst size (--burst option, default 32, max 512)
>>> for better efficiency.
>>>
>>> Fixes: d5c4897ecfb2 ("examples/l3fwd: add option to set Rx burst size")
>>> Cc: haijie1@huawei.com
>>> Cc: stable@dpdk.org
>>>
>>> Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
>>> Tested-by: Venkat Kumar Ande <VenkatKumar.Ande@amd.com>
>>> Tested-by: Dengdui Huang <huangdengdui@huawei.com>
>
>> It would be good if the selected burst sizes of Rx and Tx are logged.
> ACK
>
>> On CN10K platform we see upto 5% improvement, and upto 30% improvement on CN9K.
>
>> Tested-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
>> ---
>> examples/l3fwd/l3fwd.h        |  8 ++------
>> examples/l3fwd/l3fwd_common.h | 11 +++++++----
>> examples/l3fwd/main.c         |  2 ++
>> 3 files changed, 11 insertions(+), 10 deletions(-)
>
>


[-- Attachment #2: Type: text/html, Size: 6448 bytes --]

      reply	other threads:[~2025-11-01 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  4:54 [PATCH] " Sivaprasad Tummala
2025-02-12  9:17 ` Ande, Venkat Kumar
2025-02-12  9:46 ` Ande, Venkat Kumar
2025-02-19 16:59 ` Konstantin Ananyev
2025-05-08  1:44 ` huangdengdui
2025-06-09  9:58 ` [PATCH v2] " Sivaprasad Tummala
2025-06-09 15:21   ` Stephen Hemminger
2025-06-10  6:42     ` huangdengdui
2025-06-10  7:57       ` fengchengwen
2025-06-10 14:29   ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-10-09  2:32     ` Tummala, Sivaprasad
2025-10-31  9:18       ` fengchengwen
2025-11-01 12:53         ` Tummala, Sivaprasad [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=CH3PR12MB8233D6BB749461012556FD4986F9A@CH3PR12MB8233.namprd12.prod.outlook.com \
    --to=sivaprasad.tummala@amd.com \
    --cc=Ferruh.Yigit@amd.com \
    --cc=VenkatKumar.Ande@amd.com \
    --cc=anatoly.burakov@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=gakhil@marvell.com \
    --cc=haijie1@huawei.com \
    --cc=huangdengdui@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=konstantin.ananyev@huawei.com \
    --cc=mb@smartsharesystems.com \
    --cc=pbhagavatula@marvell.com \
    --cc=radu.nicolau@intel.com \
    --cc=stable@dpdk.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).