From: Thomas Monjalon <thomas@monjalon.net>
To: Chengwen Feng <fengchengwen@huawei.com>
Cc: stephen@networkplumber.org, dev@dpdk.org,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: Re: [PATCH v4] examples/l3fwd: dynamic NUMA-aware alloc lcore_conf
Date: Thu, 12 Nov 2026 22:00:53 +0100 [thread overview]
Message-ID: <ePWBbDOaRuCbdpFEqlBxbw@monjalon.net> (raw)
In-Reply-To: <08a81384-6088-4a20-982a-91843b2ac604@yandex.ru>
> > Currently lcore_conf is a global static array. When multiple
> > ports/lcores are distributed across different NUMA nodes, datapath
> > suffers from severe cross-NUMA memory access penalty.
> >
> > On Kunpeng platform, sizeof(struct lcore_conf) reaches 133760 bytes.
> > Such a huge per-lcore structure significantly amplifies cross-NUMA
> > overhead in multi-port multi-NUMA deployment scenarios.
> >
> > This commit refactors lcore_conf to pointer array and implements
> > per-lcore NUMA-aware hugepage allocation, allocating each lcore's
> > configuration on its local socket to eliminate remote memory access.
> >
> > Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
>
> Acked-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Applied, thanks.
prev parent reply other threads:[~2026-11-12 21:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 3:23 [PATCH] examples/l3fwd: dynamic NUMA-aware alloc lcore_conf Chengwen Feng
2026-06-24 3:23 ` [PATCH v2] " Chengwen Feng
2026-06-24 4:26 ` Stephen Hemminger
2026-06-24 6:05 ` fengchengwen
2026-07-12 0:36 ` Thomas Monjalon
2026-07-15 9:22 ` [PATCH] " Chengwen Feng
2026-10-29 2:54 ` [PATCH v3] " Chengwen Feng
2026-10-29 9:19 ` Konstantin Ananyev
2026-10-29 12:12 ` fengchengwen
2026-10-30 10:52 ` Konstantin Ananyev
2026-10-30 12:59 ` Thomas Monjalon
2026-10-31 1:37 ` fengchengwen
2026-11-01 14:26 ` Thomas Monjalon
2026-11-02 4:13 ` fengchengwen
2026-11-04 2:08 ` fengchengwen
2026-10-29 12:09 ` [PATCH v4] " Chengwen Feng
2026-10-30 10:48 ` Konstantin Ananyev
2026-11-12 21:00 ` Thomas Monjalon [this message]
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=ePWBbDOaRuCbdpFEqlBxbw@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=stephen@networkplumber.org \
/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