From: Randy L Tice <rtice@cisco.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>, Randy L Tice <rtice@cisco.com>
Subject: [PATCH v2 0/1] eal: add CPU socket lookup API
Date: Tue, 15 Sep 2026 11:05:06 -0400 [thread overview]
Message-ID: <20260915150507.3-1-rtice@cisco.com> (raw)
In-Reply-To: <178941409436.3.12421464753538796039@cisco.com>
Some applications need to derive socket-specific EAL configuration
from OS CPU IDs before EAL lcore IDs are useful. One example is
building socket memory policy from the CPUs available to the process.
Existing public socket APIs do not cover this directly. rte_socket_id()
reports the calling thread socket, while rte_lcore_to_socket_id()
requires an EAL lcore ID and uses EAL lcore configuration.
Add experimental rte_cpu_socket_id() as a public API for mapping an OS
logical CPU ID to the NUMA socket containing that CPU. The
implementation reuses the existing per-OS EAL lookup internally, while
keeping the eal_cpu_socket_id() helper private to EAL.
v2:
- Mark rte_cpu_socket_id() experimental in the declaration, export
macro, release note and commit message.
Randy L Tice (1):
eal: add API to get CPU socket ID
.mailmap | 1 +
doc/guides/rel_notes/release_26_11.rst | 3 +++
lib/eal/common/eal_common_lcore.c | 7 +++++++
lib/eal/include/rte_lcore.h | 18 ++++++++++++++++++
4 files changed, 29 insertions(+)
--
2.35.6
next prev parent reply other threads:[~2026-09-15 15:05 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 ` Randy L Tice [this message]
2026-09-15 15:05 ` [PATCH v2 " 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
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=20260915150507.3-1-rtice@cisco.com \
--to=rtice@cisco.com \
--cc=dev@dpdk.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 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.