From: David Marchand <david.marchand@redhat.com>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
"Huisong Li" <lihuisong@huawei.com>,
"Chengwen Feng" <fengchengwen@huawei.com>,
"Jie Hai" <haijie1@huawei.com>,
dev@dpdk.org, stable@dpdk.org,
"Venkat Kumar Ande" <venkatkumar.ande@amd.com>,
"Dengdui Huang" <huangdengdui@huawei.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>
Subject: Re: [PATCH v3] examples/l3fwd: add Tx burst size configuration option
Date: Mon, 24 Nov 2025 17:12:42 +0100 [thread overview]
Message-ID: <CAJFAV8yBJhQkUoTxpWX+L8XGWN1MdzPZ6hjFmYYVxsoaTiOu9g@mail.gmail.com> (raw)
In-Reply-To: <20251106141631.179443-1-sivaprasad.tummala@amd.com>
On Thu, 6 Nov 2025 at 15:17, Sivaprasad Tummala
<sivaprasad.tummala@amd.com> wrote:
>
> Previously, the TX burst size in l3fwd was fixed at 256, which could
> lead to suboptimal performance in certain scenarios.
>
> This patch introduces separate --rx-burst and --tx-burst options to
> explicitly configure RX and TX burst sizes. By default, the TX burst
> size now matches the RX burst size for better efficiency and pipeline
> balance.
>
> Fixes: d5c4897ecfb2 ("examples/l3fwd: add option to set Rx burst size")
>
> 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>
> Tested-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> v3:
> - Added --tx-burst option to allow independent TX burst configuration
> - Renamed --burst to --rx-burst for clarity
> - Renamed variables for clarity:
> - nb_pkt_per_burst → rx_burst_size
> - max_tx_burst → tx_burst_size
> - Modified parsing packet burst logic for RX and TX
> - Default TX burst size now equals RX burst size
> - Added logging of selected RX and TX burst sizes
> - Updated documentation for --rx-burst and --tx-burst options
Please don't put changelog in the commitlog itself.
Fixed when applying...
I also fixed [RT]X occurences as [RT]x.
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2025-11-24 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 4:54 [PATCH] examples/l3fwd: adjust Tx burst size based on Rx burst 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
2025-11-06 14:16 ` [PATCH v3] examples/l3fwd: add Tx burst size configuration option Sivaprasad Tummala
2025-11-07 0:38 ` fengchengwen
2025-11-24 16:12 ` David Marchand [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=CAJFAV8yBJhQkUoTxpWX+L8XGWN1MdzPZ6hjFmYYVxsoaTiOu9g@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=pbhagavatula@marvell.com \
--cc=sivaprasad.tummala@amd.com \
--cc=stable@dpdk.org \
--cc=venkatkumar.ande@amd.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).