From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: dev@dpdk.org, honnappa.nagarahalli@arm.com, mdr@ashroe.eu,
yipeng1.wang@intel.com
Cc: dharmik.thakkar@arm.com, nd@arm.com
Subject: [dpdk-dev] [PATCH] hash: promote APIs to stable
Date: Wed, 13 Oct 2021 16:38:58 -0500 [thread overview]
Message-ID: <20211013213858.16200-1-honnappa.nagarahalli@arm.com> (raw)
Promote rte_hash_free_key_with_position and rte_hash_rcu_qsbr_add APIs
to stable.
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Reviewed-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
---
lib/hash/rte_hash.h | 2 --
lib/hash/version.map | 4 ++--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/lib/hash/rte_hash.h b/lib/hash/rte_hash.h
index 73c415ff7e..0d3ef231b7 100644
--- a/lib/hash/rte_hash.h
+++ b/lib/hash/rte_hash.h
@@ -430,7 +430,6 @@ rte_hash_get_key_with_position(const struct rte_hash *h, const int32_t position,
* - 0 if freed successfully
* - -EINVAL if the parameters are invalid.
*/
-__rte_experimental
int
rte_hash_free_key_with_position(const struct rte_hash *h,
const int32_t position);
@@ -691,7 +690,6 @@ rte_hash_iterate(const struct rte_hash *h, const void **key, void **data, uint32
* - EEXIST - already added QSBR
* - ENOMEM - memory allocation failure
*/
-__rte_experimental
int rte_hash_rcu_qsbr_add(struct rte_hash *h, struct rte_hash_rcu_config *cfg);
#ifdef __cplusplus
diff --git a/lib/hash/version.map b/lib/hash/version.map
index ce4309aa07..85178df3f7 100644
--- a/lib/hash/version.map
+++ b/lib/hash/version.map
@@ -14,6 +14,7 @@ DPDK_22 {
rte_hash_del_key_with_hash;
rte_hash_find_existing;
rte_hash_free;
+ rte_hash_free_key_with_position;
rte_hash_get_key_with_position;
rte_hash_hash;
rte_hash_iterate;
@@ -23,6 +24,7 @@ DPDK_22 {
rte_hash_lookup_data;
rte_hash_lookup_with_hash;
rte_hash_lookup_with_hash_data;
+ rte_hash_rcu_qsbr_add;
rte_hash_reset;
rte_hash_set_cmp_func;
@@ -32,11 +34,9 @@ DPDK_22 {
EXPERIMENTAL {
global:
- rte_hash_free_key_with_position;
rte_hash_lookup_with_hash_bulk;
rte_hash_lookup_with_hash_bulk_data;
rte_hash_max_key_id;
- rte_hash_rcu_qsbr_add;
rte_thash_add_helper;
rte_thash_adjust_tuple;
rte_thash_find_existing;
--
2.25.1
next reply other threads:[~2021-10-13 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 21:38 Honnappa Nagarahalli [this message]
2021-10-13 22:41 ` Stephen Hemminger
2021-10-14 0:19 ` Honnappa Nagarahalli
2021-10-14 1:54 ` Wang, Yipeng1
2021-10-14 16:46 ` Medvedkin, Vladimir
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=20211013213858.16200-1-honnappa.nagarahalli@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dharmik.thakkar@arm.com \
--cc=mdr@ashroe.eu \
--cc=nd@arm.com \
--cc=yipeng1.wang@intel.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;
as well as URLs for NNTP newsgroup(s).