From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH] eal: make rte_lcore_cpuset and rte_lcore_to_cpu_id stable
Date: Tue, 31 Aug 2021 13:08:39 -0700 [thread overview]
Message-ID: <20210831200839.93556-1-stephen@networkplumber.org> (raw)
These were converted from inline to functions in 19.11
and should be marked as stable now.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/eal/include/rte_lcore.h | 8 --------
lib/eal/version.map | 4 ++--
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/lib/eal/include/rte_lcore.h b/lib/eal/include/rte_lcore.h
index 1550b75da0a5..cf6203a9af79 100644
--- a/lib/eal/include/rte_lcore.h
+++ b/lib/eal/include/rte_lcore.h
@@ -172,9 +172,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
@@ -182,23 +179,18 @@ 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 beeb986adcaf..14565aa10df4 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -98,9 +98,11 @@ DPDK_22 {
rte_keepalive_register_core; # WINDOWS_NO_EXPORT
rte_keepalive_register_relay_callback; # WINDOWS_NO_EXPORT
rte_lcore_count;
+ rte_lcore_cpuset;
rte_lcore_has_role;
rte_lcore_index;
rte_lcore_is_enabled;
+ rte_lcore_to_cpu_id;
rte_lcore_to_socket_id;
rte_log;
rte_log_cur_msg_loglevel;
@@ -322,8 +324,6 @@ EXPERIMENTAL {
# added in 19.08
rte_intr_ack;
- rte_lcore_cpuset;
- rte_lcore_to_cpu_id;
rte_mcfg_timer_lock;
rte_mcfg_timer_unlock;
rte_rand_max; # WINDOWS_NO_EXPORT
--
2.30.2
next reply other threads:[~2021-08-31 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 20:08 Stephen Hemminger [this message]
2021-09-01 7:04 ` Andrew Rybchenko
2021-09-01 17:16 ` Stephen Hemminger
2021-09-02 6:01 ` Andrew Rybchenko
2021-09-02 15:23 ` 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=20210831200839.93556-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).