From: fengchengwen <fengchengwen@huawei.com>
To: "Jie Hai" <haijie1@huawei.com>,
dev@dpdk.org, thomas@monjalon.net, ferruh.yigit@amd.com,
stephen@networkplumber.org, "Huisong Li" <lihuisong@huawei.com>,
"Morten Brørup" <mb@smartsharesystems.com>
Cc: <huangdengdui@huawei.com>
Subject: Re: [PATCH v2] examples/l3fwd: add option to set Tx burst size
Date: Fri, 14 Feb 2025 16:35:05 +0800 [thread overview]
Message-ID: <0f34c087-944a-475d-8f19-e6ee53d9dc74@huawei.com> (raw)
In-Reply-To: <20241204020622.977156-1-haijie1@huawei.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
On 2024/12/4 10:06, Jie Hai wrote:
> The application send packets only when the buffer is full, or the
> buffer is empty and the packets to be sent extends TX_PKT_BURST.
> The change of MAX_PKT_BURST make TX buffer size and TX_PKT_BURST
> increase, while the default cache size is 256. The packets in
> the TX direction occupy the cache. As a result, the performance
> deteriorates.
>
> Restore the default Tx burst and add option '--tx-burst' to set
> the Tx burst size. To ensure consistency, rename the option
> '--burst' to '--rx-burst'. The valid range of the user-provided
> value is (0, MAX_PKT_BURST] for both directions.
>
> Fixes: d5c4897ecfb2 ("examples/l3fwd: add option to set RX burst size")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jie Hai <haijie1@huawei.com>
prev parent reply other threads:[~2025-02-14 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 7:13 [PATCH] examples/l3fwd: fix Tx performance deteriorate Jie Hai
2024-11-22 9:14 ` lihuisong (C)
2024-11-22 11:01 ` Konstantin Ananyev
2024-11-26 7:39 ` Jie Hai
2024-11-25 19:44 ` Stephen Hemminger
2024-12-04 2:06 ` [PATCH v2] examples/l3fwd: add option to set Tx burst size Jie Hai
2025-02-14 2:11 ` Jie Hai
2025-02-19 17:01 ` Konstantin Ananyev
2025-02-21 3:42 ` Jie Hai
2025-02-21 8:45 ` Konstantin Ananyev
2025-02-14 8:35 ` fengchengwen [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=0f34c087-944a-475d-8f19-e6ee53d9dc74@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).