From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org, Ray Kinsella <mdr@ashroe.eu>
Subject: [dpdk-dev] [PATCH v1 7/7] eal: promote mcfg API's to stable
Date: Fri, 10 Sep 2021 12:30:09 +0000 [thread overview]
Message-ID: <37d174136f8f8dcaa47f875e196bf2d9ec7d5228.1631277001.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <029012e59f555be16bed829229e8b48016157371.1631277001.git.anatoly.burakov@intel.com>
As per ABI policy, move the formerly experimental API's to the stable
section.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
lib/eal/include/rte_eal_memconfig.h | 12 ------------
lib/eal/version.map | 8 +++-----
2 files changed, 3 insertions(+), 17 deletions(-)
diff --git a/lib/eal/include/rte_eal_memconfig.h b/lib/eal/include/rte_eal_memconfig.h
index dede2ee324..44f5324906 100644
--- a/lib/eal/include/rte_eal_memconfig.h
+++ b/lib/eal/include/rte_eal_memconfig.h
@@ -92,33 +92,21 @@ void
rte_mcfg_mempool_write_unlock(void);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
* Lock the internal EAL Timer Library lock for exclusive access.
*/
-__rte_experimental
void
rte_mcfg_timer_lock(void);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
* Unlock the internal EAL Timer Library lock for exclusive access.
*/
-__rte_experimental
void
rte_mcfg_timer_unlock(void);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
* If true, pages are put in single files (per memseg list),
* as opposed to creating a file per page.
*/
-__rte_experimental
bool
rte_mcfg_get_single_file_segments(void);
diff --git a/lib/eal/version.map b/lib/eal/version.map
index ebafb05e90..ec05d1164b 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -160,6 +160,7 @@ DPDK_22 {
rte_malloc_socket;
rte_malloc_validate;
rte_malloc_virt2iova;
+ rte_mcfg_get_single_file_segments;
rte_mcfg_mem_read_lock;
rte_mcfg_mem_read_unlock;
rte_mcfg_mem_write_lock;
@@ -172,6 +173,8 @@ DPDK_22 {
rte_mcfg_tailq_read_unlock;
rte_mcfg_tailq_write_lock;
rte_mcfg_tailq_write_unlock;
+ rte_mcfg_timer_lock;
+ rte_mcfg_timer_unlock;
rte_mem_alloc_validator_register;
rte_mem_alloc_validator_unregister;
rte_mem_check_dma_mask;
@@ -320,13 +323,8 @@ EXPERIMENTAL {
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
- # added in 19.11
- rte_mcfg_get_single_file_segments;
-
# added in 20.02
rte_thread_is_intr;
--
2.25.1
next prev parent reply other threads:[~2021-09-10 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 12:30 [dpdk-dev] [PATCH v1 1/7] eal: promote IPC " Anatoly Burakov
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 2/7] fbarray: promote " Anatoly Burakov
2021-09-10 15:52 ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 3/7] eal: promote malloc " Anatoly Burakov
2021-09-10 15:53 ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 4/7] mem: promote memseg " Anatoly Burakov
2021-09-10 15:55 ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 5/7] mem: promote extmem " Anatoly Burakov
2021-09-10 15:56 ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 6/7] mem: promote DMA mask " Anatoly Burakov
2021-09-10 15:56 ` Kinsella, Ray
2021-09-10 12:30 ` Anatoly Burakov [this message]
2021-09-10 16:23 ` [dpdk-dev] [PATCH v1 7/7] eal: promote mcfg " Kinsella, Ray
2021-09-10 15:51 ` [dpdk-dev] [PATCH v1 1/7] eal: promote IPC " Kinsella, Ray
2021-09-29 5:48 ` 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=37d174136f8f8dcaa47f875e196bf2d9ec7d5228.1631277001.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.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).