From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Ray Kinsella <mdr@ashroe.eu>
Subject: [PATCH 2/4] lcore: change rte_lcore_to_cpu_id and rte_lcore_cpuset as not experimental
Date: Wed, 16 Feb 2022 11:39:15 -0800 [thread overview]
Message-ID: <20220216193917.251657-3-stephen@networkplumber.org> (raw)
In-Reply-To: <20220216193917.251657-1-stephen@networkplumber.org>
These API's have been around for a long time and by now are fixed.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/eal/include/rte_lcore.h | 9 +--------
lib/eal/version.map | 4 ++--
2 files changed, 3 insertions(+), 10 deletions(-)
diff --git a/lib/eal/include/rte_lcore.h b/lib/eal/include/rte_lcore.h
index 258bc49b24ea..d2f908fa3466 100644
--- a/lib/eal/include/rte_lcore.h
+++ b/lib/eal/include/rte_lcore.h
@@ -160,9 +160,6 @@ unsigned int
rte_lcore_to_socket_id(unsigned int lcore_id);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Return the id of the lcore on a socket starting from zero.
*
* @param lcore_id
@@ -170,23 +167,19 @@ rte_lcore_to_socket_id(unsigned int lcore_id);
* @return
* The relative index, or -1 if not enabled.
*/
-__rte_experimental
int
rte_lcore_to_cpu_id(int lcore_id);
#ifdef RTE_HAS_CPUSET
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Return the cpuset for a given lcore.
+ *
* @param lcore_id
* the targeted lcore, which MUST be between 0 and RTE_MAX_LCORE-1.
* @return
* The cpuset of that lcore
*/
-__rte_experimental
rte_cpuset_t
rte_lcore_cpuset(unsigned int lcore_id);
diff --git a/lib/eal/version.map b/lib/eal/version.map
index 6b1657d0d8bd..18d46acfeb1e 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -122,11 +122,13 @@ DPDK_22 {
rte_lcore_callback_register;
rte_lcore_callback_unregister;
rte_lcore_count;
+ rte_lcore_cpuset;
rte_lcore_dump;
rte_lcore_has_role;
rte_lcore_index;
rte_lcore_is_enabled;
rte_lcore_iterate;
+ rte_lcore_to_cpu_id;
rte_lcore_to_socket_id;
rte_log;
rte_log_can_log;
@@ -322,8 +324,6 @@ EXPERIMENTAL {
# added in 19.08
rte_intr_ack;
- rte_lcore_cpuset;
- rte_lcore_to_cpu_id;
# added in 20.02
rte_thread_is_intr;
--
2.34.1
next prev parent reply other threads:[~2022-02-16 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 19:39 [PATCH 0/4] eal: remove some experimental tags Stephen Hemminger
2022-02-16 19:39 ` [PATCH 1/4] rte_log: take of " Stephen Hemminger
2022-02-17 12:57 ` Ray Kinsella
2022-02-16 19:39 ` Stephen Hemminger [this message]
2022-02-17 12:55 ` [PATCH 2/4] lcore: change rte_lcore_to_cpu_id and rte_lcore_cpuset as not experimental Ray Kinsella
2022-02-16 19:39 ` [PATCH 3/4] eal: make some intr functions " Stephen Hemminger
2022-02-17 12:56 ` Ray Kinsella
2022-02-16 19:39 ` [PATCH 4/4] eal: mark rte_delay_us_sleep as " Stephen Hemminger
2022-02-17 12:56 ` Ray Kinsella
2022-06-26 15:34 ` [PATCH 0/4] eal: remove some experimental tags Thomas Monjalon
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=20220216193917.251657-3-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
/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;
as well as URLs for NNTP newsgroup(s).