From: Liangxing Wang <wangliangxing@hygon.cn>
To: <thomas@monjalon.net>, <stephen@networkplumber.org>,
<fengchengwen@huawei.com>
Cc: <dev@dpdk.org>, Liangxing Wang <wangliangxing@hygon.cn>,
<stable@dpdk.org>
Subject: [PATCH v2 1/3] examples/l3fwd: extend NUMA nodes limit beyond 8
Date: Thu, 8 Jan 2026 07:29:19 +0000 [thread overview]
Message-ID: <20260108072919.1279731-1-wangliangxing@hygon.cn> (raw)
For platforms with more than 8 NUMA nodes, examples l3fwd, l3fwd-graph,
and l3fwd-power fail when using cores on NUMA node 8 or above.
Use RTE_MAX_NUMA_NODES instead of 8 to extend NUMA nodes limit.
Cc: stable@dpdk.org
Signed-off-by: Liangxing Wang <wangliangxing@hygon.cn>
---
examples/l3fwd-graph/main.c | 2 +-
examples/l3fwd-power/main.c | 2 +-
examples/l3fwd/l3fwd.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/examples/l3fwd-graph/main.c b/examples/l3fwd-graph/main.c
index 92cdaa1ebe..d77b5f4ef6 100644
--- a/examples/l3fwd-graph/main.c
+++ b/examples/l3fwd-graph/main.c
@@ -56,7 +56,7 @@
#define MAX_LCORE_PARAMS 1024
-#define NB_SOCKETS 8
+#define NB_SOCKETS RTE_MAX_NUMA_NODES
/* Graph module */
#define WORKER_MODEL_RTC "rtc"
diff --git a/examples/l3fwd-power/main.c b/examples/l3fwd-power/main.c
index ec12d1cc0b..534e438d0b 100644
--- a/examples/l3fwd-power/main.c
+++ b/examples/l3fwd-power/main.c
@@ -115,7 +115,7 @@ RTE_LOG_REGISTER(l3fwd_power_logtype, l3fwd.power, INFO);
#define BURST_TX_DRAIN_US 100 /* TX drain every ~100us */
-#define NB_SOCKETS 8
+#define NB_SOCKETS RTE_MAX_NUMA_NODES
/* Configure how many packets ahead to prefetch, when reading packets */
#define PREFETCH_OFFSET 3
diff --git a/examples/l3fwd/l3fwd.h b/examples/l3fwd/l3fwd.h
index 471e3b488f..ca9d0d2dd0 100644
--- a/examples/l3fwd/l3fwd.h
+++ b/examples/l3fwd/l3fwd.h
@@ -33,7 +33,7 @@
#define VECTOR_SIZE_DEFAULT MAX_PKT_BURST
#define VECTOR_TMO_NS_DEFAULT 1E6 /* 1ms */
-#define NB_SOCKETS 8
+#define NB_SOCKETS RTE_MAX_NUMA_NODES
/* Configure how many packets ahead to prefetch, when reading packets */
#define PREFETCH_OFFSET 3
--
2.43.0
reply other threads:[~2026-01-08 7:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260108072919.1279731-1-wangliangxing@hygon.cn \
--to=wangliangxing@hygon.cn \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=stable@dpdk.org \
--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).