From: Vipin Varghese <vipin.varghese@amd.com>
To: <dev@dpdk.org>, <sivaprasad.tummala@amd.com>
Cc: <konstantin.ananyev@huawei.com>, <wathsala.vithanage@arm.com>,
<bruce.richardson@intel.com>, <viktorin@cesnet.cz>,
<mb@smartsharesystems.com>
Subject: [PATCH v5 v5 3/3] doc: add new section topology
Date: Wed, 15 Apr 2026 01:08:21 +0530 [thread overview]
Message-ID: <20260414193850.1696-4-vipin.varghese@amd.com> (raw)
In-Reply-To: <20260414193850.1696-1-vipin.varghese@amd.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="y", Size: 5242 bytes --]
changes:
- add new section under utility
- include rte_topo API and usuage
Signed-off-by: Vipin Varghese <vipin.varghese@amd.com>
---
doc/api/doxy-api-index.md | 1 +
doc/guides/prog_guide/index.rst | 3 +-
doc/guides/prog_guide/topology_lib.rst | 155 +++++++++++++++++++++++++
3 files changed, 158 insertions(+), 1 deletion(-)
create mode 100644 doc/guides/prog_guide/topology_lib.rst
diff --git a/doc/api/doxy-api-index.md b/doc/api/doxy-api-index.md
index 9296042119..e8655fb956 100644
--- a/doc/api/doxy-api-index.md
+++ b/doc/api/doxy-api-index.md
@@ -102,6 +102,7 @@ The public API headers are grouped by topics:
[interrupts](@ref rte_interrupts.h),
[launch](@ref rte_launch.h),
[lcore](@ref rte_lcore.h),
+ [topology](@ref rte_topology.h),
[service cores](@ref rte_service.h),
[keepalive](@ref rte_keepalive.h),
[power/freq](@ref rte_power_cpufreq.h),
diff --git a/doc/guides/prog_guide/index.rst b/doc/guides/prog_guide/index.rst
index e6f24945b0..8e1153acef 100644
--- a/doc/guides/prog_guide/index.rst
+++ b/doc/guides/prog_guide/index.rst
@@ -133,9 +133,10 @@ Utility Libraries
pcapng_lib
bpf_lib
trace_lib
+ topology_lib
-Howto Guides
+How to Guides
-------------
.. toctree::
diff --git a/doc/guides/prog_guide/topology_lib.rst b/doc/guides/prog_guide/topology_lib.rst
new file mode 100644
index 0000000000..42af7e5793
--- /dev/null
+++ b/doc/guides/prog_guide/topology_lib.rst
@@ -0,0 +1,155 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+ Copyright(c) 2026 AMD Inc.
+
+Topology Library
+================
+
+Overview
+--------
+
+The Topology library provides NUMA‑aware grouping of DPDK logical cores
+based on CPU-CACHE and I/O topology.
+
+It exposes APIs that allow applications to query topology domains and
+enumerate logical cores within those domains. This enables topology‑aware
+core selection for improved locality and performance.
+
+The library integrates with the ``hwloc`` library to obtain hardware
+topology information while maintaining ABI stability.
+
+Motivation
+----------
+
+Application performance can be improved when:
+
+- DPDK libraries and PMDs operate within the same topology domain
+- Cache sharing is maximized in pipeline and graph applications
+- Cache identifiers (L2/L3) are used for:
+ - Data placement
+ - Platform QoS (PQoS) configuration
+
+This library provides a consistent topology view, including support for
+EAL lcore reordering via the ``-R`` option.
+
+Functionality
+-------------
+
+The Topology library provides the following functionality:
+
+- Partitioning of logical cores into topology domains
+- Support for CPU and I/O based domain selection
+- Grouping of lcores by hierarchy levels: L1, L2, L3, L4, IO
+- Reverse lookup from lcore to domain index
+- Helper APIs for lcore and domain iteration
+
+Dependencies
+------------
+
+- ``hwloc-dev`` tested on `2.10.0`
+
+The dependency is used to:
+
+- Discover system topology
+- Group logical cores into DPDK‑specific domains
+- Provide stable mappings across EAL configurations
+
+API Overview
+------------
+
+All APIs are provided under the ``RTE_TOPO`` namespace.
+
+Domain Enumeration
+------------------
+
+Get the number of domains for a selected topology type.
+
+.. code-block:: c
+
+ uint32_t
+ rte_topo_get_domain_count(enum rte_topo_domain_sel domain_sel);
+
+Lcore Enumeration
+-----------------
+
+Enumerate logical cores within a topology domain.
+
+.. code-block:: c
+
+ uint32_t
+ rte_topo_get_lcore_count_from_domain(
+ enum rte_topo_domain_sel domain_sel,
+ uint32_t domain_idx);
+
+ unsigned int
+ rte_topo_get_nth_lcore_in_domain(
+ enum rte_topo_domain_sel domain_sel,
+ uint32_t domain_idx,
+ uint32_t lcore_pos);
+
+Iterate over logical cores with optional filtering.
+
+.. code-block:: c
+
+ unsigned int
+ rte_topo_get_next_lcore(
+ unsigned int lcore,
+ bool skip_main,
+ bool wrap,
+ uint32_t flag);
+
+ unsigned int
+ rte_topo_get_nth_lcore_from_domain(
+ uint32_t domain_idx,
+ uint32_t lcore_pos,
+ bool wrap,
+ uint32_t flag);
+
+Domain Lookup
+-------------
+
+Query the domain associated with a logical core.
+
+.. code-block:: c
+
+ int
+ rte_topo_get_domain_index_from_lcore(
+ enum rte_topo_domain_sel domain_sel,
+ unsigned int lcore);
+
+Check whether the main lcore belongs to a domain.
+
+.. code-block:: c
+
+ bool
+ rte_topo_is_main_lcore_in_domain(
+ enum rte_topo_domain_sel domain_sel,
+ uint32_t domain_idx);
+
+CPU Set Access
+--------------
+
+Retrieve the CPU set associated with a topology domain.
+
+.. code-block:: c
+
+ const rte_cpuset_t *
+ rte_topo_get_lcore_cpuset_in_domain(
+ enum rte_topo_domain_sel domain_sel,
+ uint32_t domain_idx);
+
+Debug Support
+-------------
+
+Dump topology information for debugging purposes.
+
+.. code-block:: c
+
+ void
+ rte_topo_dump(FILE *f);
+
+Usage Notes
+-----------
+
+- Domain‑aware lcore selection can reduce remote memory access.
+- Cache‑level domains are suitable for cache‑sensitive workloads.
+- Topology mappings remain stable across EAL lcore configurations.
--
2.43.0
next prev parent reply other threads:[~2026-04-14 19:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 10:28 [PATCH v4 0/4] Introduce Topology NUMA grouping for lcores Vipin Varghese
2024-11-05 10:28 ` [PATCH v4 1/4] eal/lcore: add topology based functions Vipin Varghese
2024-11-05 10:28 ` [PATCH v4 2/4] test/lcore: enable tests for topology Vipin Varghese
2024-11-05 10:28 ` [PATCH v4 3/4] doc: add topology grouping details Vipin Varghese
2024-11-05 10:28 ` [PATCH v4 4/4] examples: update with lcore topology API Vipin Varghese
2025-02-13 3:09 ` [PATCH v4 0/4] Introduce Topology NUMA grouping for lcores Varghese, Vipin
2025-02-13 8:34 ` Thomas Monjalon
2025-02-13 9:18 ` Morten Brørup
2025-03-03 9:06 ` Varghese, Vipin
2025-03-04 10:08 ` Morten Brørup
2025-03-05 7:43 ` Mattias Rönnblom
2025-03-03 8:59 ` Varghese, Vipin
2025-03-17 13:46 ` Jan Viktorin
2025-04-09 10:08 ` Varghese, Vipin
2025-06-03 6:03 ` Varghese, Vipin
2026-01-17 18:57 ` Stephen Hemminger
2026-01-19 14:55 ` [PATCH v4 0/4] Introduce Topology NUMA grouping for cores Varghese, Vipin
2026-04-14 19:38 ` [PATCH v5 0/3] eal/topology: introduce topology-aware lcore grouping Vipin Varghese
2026-04-14 19:38 ` [PATCH v5 v5 1/3] eal/topology: add Topology grouping for lcores Vipin Varghese
2026-04-15 14:06 ` Morten Brørup
2026-04-15 17:52 ` Varghese, Vipin
2026-04-14 19:38 ` [PATCH v5 v5 2/3] app: add topology aware test case Vipin Varghese
2026-04-15 5:21 ` Sudheendra Sampath
2026-04-16 7:22 ` Varghese, Vipin
2026-04-16 13:19 ` Varghese, Vipin
2026-04-17 1:21 ` Varghese, Vipin
2026-04-17 5:19 ` Sudheendra Sampath
2026-04-17 9:55 ` Varghese, Vipin
2026-04-14 19:38 ` Vipin Varghese [this message]
2026-04-14 20:22 ` [PATCH v5 0/3] eal/topology: introduce topology-aware lcore grouping 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=20260414193850.1696-4-vipin.varghese@amd.com \
--to=vipin.varghese@amd.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=mb@smartsharesystems.com \
--cc=sivaprasad.tummala@amd.com \
--cc=viktorin@cesnet.cz \
--cc=wathsala.vithanage@arm.com \
/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