DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Subject: [PATCH v3 2/6] examples/l3fwd: remove redundant Tx queue limit
Date: Thu, 25 Jun 2026 10:46:52 -0700	[thread overview]
Message-ID: <20260625174908.278408-3-stephen@networkplumber.org> (raw)
In-Reply-To: <20260625174908.278408-1-stephen@networkplumber.org>

From: Sivaprasad Tummala <sivaprasad.tummala@amd.com>

In `l3fwd` 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_LCORE`
which is dead code.

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

diff --git a/examples/l3fwd/main.c b/examples/l3fwd/main.c
index df035b508c..6866811526 100644
--- a/examples/l3fwd/main.c
+++ b/examples/l3fwd/main.c
@@ -48,7 +48,6 @@
 #include "l3fwd_event.h"
 #include "l3fwd_route.h"
 
-#define MAX_TX_QUEUE_PER_PORT RTE_MAX_LCORE
 #define MAX_RX_QUEUE_PER_PORT 128
 
 #define MAX_LCORE_PARAMS 1024
@@ -1373,8 +1372,6 @@ l3fwd_poll_resource_setup(void)
 
 		nb_rx_queue = get_port_n_rx_queues(portid);
 		n_tx_queue = nb_lcores;
-		if (n_tx_queue > MAX_TX_QUEUE_PER_PORT)
-			n_tx_queue = MAX_TX_QUEUE_PER_PORT;
 		printf("Creating queues: nb_rxq=%d nb_txq=%u... ",
 			nb_rx_queue, (unsigned)n_tx_queue );
 
-- 
2.53.0


  parent reply	other threads:[~2026-06-25 17:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 15:44 [PATCH] examples/l3fwd-graph: remove redundant Tx queue limit 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   ` [PATCH v2 3/5] examples/ip_fragmentation: " Sivaprasad Tummala
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
2026-06-25 17:46 ` [PATCH v3 0/6] examples: remove MAX_TX_QUEUE_PER_PORT Stephen Hemminger
2026-06-25 17:46   ` [PATCH v3 1/6] examples/l3fwd-graph: remove redundant Tx queue limit Stephen Hemminger
2026-06-25 17:46   ` Stephen Hemminger [this message]
2026-06-25 17:46   ` [PATCH v3 3/6] examples/ip_fragmentation: " Stephen Hemminger
2026-06-25 17:46   ` [PATCH v3 4/6] examples/ip_reassembly: " Stephen Hemminger
2026-06-25 17:46   ` [PATCH v3 5/6] examples/ipv4_multicast: " Stephen Hemminger
2026-06-25 17:46   ` [PATCH v3 6/6] examples: remove unused define Stephen Hemminger
2026-06-26  7:23   ` [PATCH v3 0/6] examples: remove MAX_TX_QUEUE_PER_PORT Bruce Richardson

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=20260625174908.278408-3-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=sivaprasad.tummala@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