DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
To: <thomas@monjalon.net>,
	Konstantin Ananyev <konstantin.ananyev@huawei.com>
Cc: <dev@dpdk.org>, <ndabilpuram@marvell.com>, <stable@dpdk.org>
Subject: [PATCH v2 3/5] examples/ip_fragmentation: remove redundant Tx queue limit
Date: Sat, 22 Nov 2025 15:51:54 +0000	[thread overview]
Message-ID: <20251122155156.1385975-3-sivaprasad.tummala@amd.com> (raw)
In-Reply-To: <20251122155156.1385975-1-sivaprasad.tummala@amd.com>

In `ip_fragmentation` 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: af75078fece3 ("first public release")
Cc: stable@dpdk.org

Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
---
 examples/ip_fragmentation/main.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/examples/ip_fragmentation/main.c b/examples/ip_fragmentation/main.c
index 1f84102844..9be2f72983 100644
--- a/examples/ip_fragmentation/main.c
+++ b/examples/ip_fragmentation/main.c
@@ -134,7 +134,6 @@ struct rx_queue {
 };
 
 #define MAX_RX_QUEUE_PER_LCORE 16
-#define MAX_TX_QUEUE_PER_PORT 16
 struct __rte_cache_aligned lcore_queue_conf {
 	uint16_t n_rx_queue;
 	uint16_t tx_queue_id[RTE_MAX_ETHPORTS];
@@ -948,8 +947,6 @@ main(int argc, char **argv)
 		fflush(stdout);
 
 		n_tx_queue = nb_lcores;
-		if (n_tx_queue > MAX_TX_QUEUE_PER_PORT)
-			n_tx_queue = MAX_TX_QUEUE_PER_PORT;
 		ret = rte_eth_dev_configure(portid, 1, (uint16_t)n_tx_queue,
 					    &local_port_conf);
 		if (ret < 0) {
-- 
2.43.0


  parent reply	other threads:[~2025-11-22 15:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 15:44 [PATCH] examples/l3fwd-graph: " 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
2025-11-19 13:56             ` Tummala, Sivaprasad
2025-11-19 14:55               ` Thomas Monjalon
2025-11-21  4:37                 ` Tummala, Sivaprasad
2025-11-22 15:51 ` [PATCH v2 1/5] " Sivaprasad Tummala
2025-11-22 15:51   ` [PATCH v2 2/5] examples/l3fwd: " Sivaprasad Tummala
2025-11-22 15:51   ` Sivaprasad Tummala [this message]
2025-11-22 15:51   ` [PATCH v2 4/5] examples/ip_reassembly: " Sivaprasad Tummala
2025-11-22 15:51   ` [PATCH v2 5/5] examples/ipv4_multicast: " Sivaprasad Tummala

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=20251122155156.1385975-3-sivaprasad.tummala@amd.com \
    --to=sivaprasad.tummala@amd.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@huawei.com \
    --cc=ndabilpuram@marvell.com \
    --cc=stable@dpdk.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).