From: Thomas Monjalon <thomas@monjalon.net>
To: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
Cc: Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Nithin Dabilpuram <nithind1988@gmail.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"kirankumark@marvell.com" <kirankumark@marvell.com>,
"ndabilpuram@marvell.com" <ndabilpuram@marvell.com>,
"yanzhirun_163@163.com" <yanzhirun_163@163.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"aconole@redhat.com" <aconole@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] examples/l3fwd-graph: remove redundant Tx queue limit
Date: Wed, 19 Nov 2025 13:57:12 +0100 [thread overview]
Message-ID: <3175023.Icojqenx9y@thomas> (raw)
In-Reply-To: <CH3PR12MB823340B751F8D8DFA890146686D7A@CH3PR12MB8233.namprd12.prod.outlook.com>
19/11/2025 13:08, Tummala, Sivaprasad:
> From: Thomas Monjalon <thomas@monjalon.net>
> 06/10/2025 10:58, Tummala, Sivaprasad:
> > From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
> > > > On Mon, Sep 1, 2025 at 11:39 PM Sivaprasad Tummala
> > > > <sivaprasad.tummala@amd.com> wrote:
> > > > >
> > > > > In `l3fwd-graph` application, Tx queues are configured per lcore
> > > > > to enable a lockless design and achieve optimal performance.
> > > > >
> > > > > The `MAX_TX_QUEUE_PER_PORT` macro, defined as `RTE_MAX_ETHPORTS`,
> > > > > introduced an artificial constraint on the number of Tx queues
> > > > > and limited core-scaling performance.
> > > > >
> > > > > This patch removes the unused `MAX_TX_QUEUE_PER_PORT` macro and
> > > > > redundant Tx queue check, allowing Tx queues to scale directly
> > > > > with the no. of lcores.
> > > > >
> > > > > Fixes: 08bd1a174461 ("examples/l3fwd-graph: add graph-based l3fwd skeleton")
> > > > > Cc: ndabilpuram@marvell.com
> > > > > Cc: stable@dpdk.org
> > > > >
> > > > > Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
> > > > > ---
> > > > > examples/l3fwd-graph/main.c | 3 ---
> > > > > 1 file changed, 3 deletions(-)
> > > > >
> > > > > diff --git a/examples/l3fwd-graph/main.c b/examples/l3fwd-graph/main.c
> > > > > index 92cdaa1ebe..12908acbba 100644
> > > > > --- a/examples/l3fwd-graph/main.c
> > > > > +++ b/examples/l3fwd-graph/main.c
> > > > > @@ -49,7 +49,6 @@
> > > > > #define RX_DESC_DEFAULT 1024
> > > > > #define TX_DESC_DEFAULT 1024
> > > > >
> > > > > -#define MAX_TX_QUEUE_PER_PORT RTE_MAX_ETHPORTS
> > > > > #define MAX_RX_QUEUE_PER_PORT 128
> > >
> > > AFAIK, in the mainline we actually have:
> > > #define MAX_TX_QUEUE_PER_PORT RTE_MAX_LCORE
> > >
> > In l3fwd-graph app, this change is not available and instead we have
> >> #define MAX_TX_QUEUE_PER_PORT RTE_MAX_ETHPORTS
> >>
> >> > since:
> >> > commit 88256ed85338c572d73006e4c4530a52d3b477ff
> >> > Author: Harman Kalra <hkalra@marvell.com>
> >> > Date: Tue Jan 12 23:54:46 2021 +0530
> >> >
> >> > examples/l3fwd: remove limitation on Tx queue count
> >> >
> >> > What I am missing here?
> >> This patch marked here was fixing l3fwd app and not l3fwd-graph
>
> > Why not applying the same change to both examples?
> Yes, that's what the patch is intended for to fix l3fwd-graph and tx queues will scale with lcores and limited by RTE_MAX_LCORES.
But it is not done the same way.
Here you remove MAX_TX_QUEUE_PER_PORT.
Do you want to do the same in l3fwd?
next prev parent reply other threads:[~2025-11-19 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 15:44 Sivaprasad Tummala
2025-09-22 5:52 ` Nithin Dabilpuram
2025-09-22 6:49 ` Konstantin Ananyev
2025-10-06 8:58 ` Tummala, Sivaprasad
2025-11-18 17:09 ` Thomas Monjalon
2025-11-19 12:08 ` Tummala, Sivaprasad
2025-11-19 12:57 ` Thomas Monjalon [this message]
2025-11-19 13:56 ` Tummala, Sivaprasad
2025-11-19 14:55 ` Thomas Monjalon
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=3175023.Icojqenx9y@thomas \
--to=thomas@monjalon.net \
--cc=Sivaprasad.Tummala@amd.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.ananyev@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=nithind1988@gmail.com \
--cc=stable@dpdk.org \
--cc=yanzhirun_163@163.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).