From: Liangxing Wang <wangliangxing@hygon.cn>
To: fengchengwen <fengchengwen@huawei.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v3 0/2] Extend NUMA nodes limit
Date: Mon, 23 Mar 2026 10:00:35 +0000 [thread overview]
Message-ID: <969e9f14c78447e9af12df1415339cb7@hygon.cn> (raw)
In-Reply-To: <ac35b365-8efe-4930-99ee-1d68a92cc972@huawei.com>
Hi Thomas,
Friendly ping for review/upstream.
Regards,
Liangxing
> -----Original Message-----
> From: fengchengwen <fengchengwen@huawei.com>
> Sent: 2026年2月26日 10:11
> To: Liangxing Wang <wangliangxing@hygon.cn>; thomas@monjalon.net;
> stephen@networkplumber.org
> Cc: dev@dpdk.org
> Subject: Re: [PATCH v3 0/2] Extend NUMA nodes limit
>
> Series-acked-by: Chengwen Feng <fengchengwen@huawei.com>
>
> On 2/25/2026 4:04 PM, Liangxing Wang wrote:
> > This patchset use RTE_MAX_NUMA_NODES instead of hardcoded values to
> > extend NUMA nodes limit for some examples and test app. Also remove
> > unused NB_SOCKETS macro for ip_reassembly example and graph app.
> >
> > Liangxing Wang (2):
> > examples: extend NUMA nodes limit
> > app: extend NUMA nodes limit
> >
> > app/graph/ethdev_rx_priv.h | 1 -
> > app/test/test_pmd_perf.c | 2 +-
> > examples/ip_reassembly/main.c | 2 --
> > examples/ipsec-secgw/ipsec-secgw.h | 2 +-
> > examples/l3fwd-graph/main.c | 2 +-
> > examples/l3fwd-power/main.c | 2 +-
> > examples/l3fwd/l3fwd.h | 2 +-
> > examples/vhost_crypto/main.c | 2 +-
> > 8 files changed, 6 insertions(+), 9 deletions(-)
> >
>
next prev parent reply other threads:[~2026-03-23 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 8:04 [PATCH v3 0/2] Extend NUMA nodes limit Liangxing Wang
2026-02-26 2:11 ` fengchengwen
2026-03-23 10:00 ` Liangxing Wang [this message]
2026-05-06 8:20 ` Liangxing Wang
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=969e9f14c78447e9af12df1415339cb7@hygon.cn \
--to=wangliangxing@hygon.cn \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--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