From: Harman Kalra <hkalra@marvell.com>
To: <dev@dpdk.org>, Ray Kinsella <mdr@ashroe.eu>
Cc: Harman Kalra <hkalra@marvell.com>
Subject: [dpdk-dev] [PATCH] metrics: promote metrics deinitialize API
Date: Fri, 3 Sep 2021 18:38:03 +0530 [thread overview]
Message-ID: <20210903130803.103371-1-hkalra@marvell.com> (raw)
Remove experimental flag from rte_metrics_deinit().
This API was introduced in 19.11 release.
Signed-off-by: Harman Kalra <hkalra@marvell.com>
---
lib/metrics/rte_metrics.h | 4 ----
lib/metrics/version.map | 2 +-
2 files changed, 1 insertion(+), 5 deletions(-)
diff --git a/lib/metrics/rte_metrics.h b/lib/metrics/rte_metrics.h
index fbe64ddf2b..c2815a252c 100644
--- a/lib/metrics/rte_metrics.h
+++ b/lib/metrics/rte_metrics.h
@@ -83,9 +83,6 @@ struct rte_metric_value {
void rte_metrics_init(int socket_id);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
* Deinitialize metric module. This function must be called from
* a primary process after all the metrics usage is over, to
* release the shared memory.
@@ -96,7 +93,6 @@ void rte_metrics_init(int socket_id);
* (rte_metrics_init() not called)
* 0 - success
*/
-__rte_experimental
int rte_metrics_deinit(void);
/**
diff --git a/lib/metrics/version.map b/lib/metrics/version.map
index c86e405971..03bfdff569 100644
--- a/lib/metrics/version.map
+++ b/lib/metrics/version.map
@@ -8,6 +8,7 @@ DPDK_22 {
rte_metrics_reg_names;
rte_metrics_update_value;
rte_metrics_update_values;
+ rte_metrics_deinit;
local: *;
};
@@ -15,7 +16,6 @@ DPDK_22 {
EXPERIMENTAL {
global:
- rte_metrics_deinit;
rte_metrics_tel_encode_json_format;
rte_metrics_tel_reg_all_ethdev;
rte_metrics_tel_get_global_stats;
--
2.18.0
next reply other threads:[~2021-09-03 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 13:08 Harman Kalra [this message]
2021-09-03 13:09 ` Kinsella, Ray
2021-09-23 17:24 ` 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=20210903130803.103371-1-hkalra@marvell.com \
--to=hkalra@marvell.com \
--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).