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 v3 0/1] eal: add CPU socket lookup API
Date: Wed, 16 Sep 2026 10:55:15 -0400 [thread overview]
Message-ID: <20260916145516.3-1-rtice@cisco.com> (raw)
In-Reply-To: <20260915150507.3-1-rtice@cisco.com>
Applications may need to build socket-specific EAL policy before they have
an EAL lcore ID for each relevant CPU. Existing public APIs expose the
current thread socket, socket IDs by EAL socket index, or sockets for EAL
lcore IDs, but do not directly map an OS logical CPU ID to its NUMA socket.
Add experimental rte_cpu_socket_id() for that lookup while keeping the
existing eal_cpu_socket_id() helper private to EAL.
v3:
- Return SOCKET_ID_ANY for invalid CPU IDs and document that behavior.
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 | 11 +++++++++++
lib/eal/include/rte_lcore.h | 19 +++++++++++++++++++
4 files changed, 34 insertions(+)
--
2.35.6
next prev parent reply other threads:[~2026-09-16 14:55 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 ` Randy L Tice [this message]
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=20260916145516.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.