From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Sivaprasad Tummala <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>,
"Ferruh.Yigit@amd.com" <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>,
Venkat Kumar Ande <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: Tue, 10 Jun 2025 14:29:42 +0000 [thread overview]
Message-ID: <PH0PR18MB40861D909AD3BC9A0695309ADE6AA@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250609095827.4174387-1-sivaprasad.tummala@amd.com>
>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.
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(-)
prev parent reply other threads:[~2025-06-10 14:29 UTC|newest]
Thread overview: 10+ 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 ` Pavan Nikhilesh Bhagavatula [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=PH0PR18MB40861D909AD3BC9A0695309ADE6AA@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.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=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=radu.nicolau@intel.com \
--cc=sivaprasad.tummala@amd.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).