From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: [PATCH 3/3] eal: mark rte_memzone_max_get/set stable
Date: Wed, 4 Sep 2024 11:08:46 -0700 [thread overview]
Message-ID: <20240904180954.104473-4-stephen@networkplumber.org> (raw)
In-Reply-To: <20240904180954.104473-1-stephen@networkplumber.org>
These were added in 23.03
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/eal/include/rte_memzone.h | 8 --------
lib/eal/version.map | 6 ++----
2 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/lib/eal/include/rte_memzone.h b/lib/eal/include/rte_memzone.h
index 931497f37c..e1563994d5 100644
--- a/lib/eal/include/rte_memzone.h
+++ b/lib/eal/include/rte_memzone.h
@@ -65,9 +65,6 @@ struct rte_memzone {
} __rte_packed;
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Set the maximum number of memzones.
*
* This function can only be called prior to rte_eal_init().
@@ -77,13 +74,9 @@ struct rte_memzone {
* @return
* 0 on success, -1 otherwise.
*/
-__rte_experimental
int rte_memzone_max_set(size_t max);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Get the maximum number of memzones.
*
* @note: The maximum value will not change after calling rte_eal_init().
@@ -91,7 +84,6 @@ int rte_memzone_max_set(size_t max);
* @return
* Maximum number of memzones.
*/
-__rte_experimental
size_t rte_memzone_max_get(void);
/**
diff --git a/lib/eal/version.map b/lib/eal/version.map
index e0fa68bbfc..c45fc55486 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -225,6 +225,8 @@ DPDK_25 {
rte_memzone_dump;
rte_memzone_free;
rte_memzone_lookup;
+ rte_memzone_max_get;
+ rte_memzone_max_set;
rte_memzone_reserve;
rte_memzone_reserve_aligned;
rte_memzone_reserve_bounded;
@@ -390,10 +392,6 @@ EXPERIMENTAL {
# added in 23.03
__rte_eal_trace_generic_blob;
- # added in 23.07
- rte_memzone_max_get;
- rte_memzone_max_set;
-
# added in 24.03
rte_vfio_get_device_info; # WINDOWS_NO_EXPORT
};
--
2.45.2
next prev parent reply other threads:[~2024-09-04 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 18:08 [PATCH 0/3] eal: mark API's as stable Stephen Hemminger
2024-09-04 18:08 ` [PATCH 1/3] eal: make rte_cpu_get_intrinsics_support stable Stephen Hemminger
2024-09-04 18:08 ` [PATCH 2/3] eal: mark rte_lcore_register_usage_cb stable Stephen Hemminger
2024-10-04 12:56 ` Robin Jarry
2024-09-04 18:08 ` Stephen Hemminger [this message]
2024-09-05 6:07 ` [PATCH 0/3] eal: mark API's as stable Morten Brørup
2024-09-05 7:58 ` David Marchand
2024-09-05 8:55 ` Morten Brørup
2024-09-05 9:03 ` David Marchand
2024-09-05 9:44 ` Morten Brørup
2024-09-05 14:01 ` Jerin Jacob
2024-09-05 14:18 ` Morten Brørup
2024-09-08 23:58 ` Stephen Hemminger
2024-09-06 8:54 ` Ferruh Yigit
2024-09-06 10:04 ` Morten Brørup
2024-09-06 14:12 ` Ferruh Yigit
2024-09-06 14:42 ` Morten Brørup
2024-09-09 4:48 ` Jerin Jacob
2024-09-06 9:34 ` Ferruh Yigit
2024-09-06 9:48 ` David Marchand
2024-09-06 11:00 ` Ferruh Yigit
2024-09-06 13:11 ` Jerin Jacob
2024-09-06 14:03 ` Ferruh Yigit
2024-09-09 4:46 ` Jerin Jacob
2024-10-30 9:10 ` David Marchand
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=20240904180954.104473-4-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.