From: Stephen Hemminger <stephen@networkplumber.org>
To: Randy L Tice <rtice@cisco.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v3 1/1] eal: add API to get CPU socket ID
Date: Fri, 18 Sep 2026 09:19:29 -0700 [thread overview]
Message-ID: <20260918091929.47cce1fb@phoenix.local> (raw)
In-Reply-To: <20260916145516.3-2-rtice@cisco.com>
On Wed, 16 Sep 2026 10:55:16 -0400
Randy L Tice <rtice@cisco.com> wrote:
> Add experimental rte_cpu_socket_id() so applications can map an OS
> logical CPU ID to its NUMA socket without requiring an EAL lcore ID.
>
> Existing public socket APIs depend on EAL lcore configuration or the
> calling thread's EAL state. They do not cover code that needs to look
> up topology by OS CPU ID, such as building socket memory policy.
>
> Reuse the existing per-OS EAL CPU socket lookup internally, while
> keeping the eal_cpu_socket_id() helper private to EAL.
>
> Signed-off-by: Randy L Tice <rtice@cisco.com>
> ---
Applied to next-net. Put the release note in the New Features section
prev parent reply other threads:[~2026-09-18 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 19:28 [PATCH 0/1] eal: add CPU socket lookup API Randy L Tice
2026-09-14 19:28 ` [PATCH 1/1] eal: add API to get CPU socket ID Randy L Tice
2026-09-14 21:19 ` Stephen Hemminger
2026-09-15 15:05 ` [PATCH v2 0/1] eal: add CPU socket lookup API Randy L Tice
2026-09-15 15:05 ` [PATCH v2 1/1] eal: add API to get CPU socket ID Randy L Tice
2026-09-15 15:09 ` [PATCH v2 0/1] eal: add CPU socket lookup API Bruce Richardson
2026-09-16 14:55 ` [PATCH v3 " Randy L Tice
2026-09-16 14:55 ` [PATCH v3 1/1] eal: add API to get CPU socket ID Randy L Tice
2026-09-18 16:19 ` Stephen Hemminger [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=20260918091929.47cce1fb@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=rtice@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.