DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)" <jgrajcia@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] eal: promote rte_mcfg_get_single_file_segment to stable ABI
Date: Mon, 13 Sep 2021 08:44:13 +0000	[thread overview]
Message-ID: <CY4PR1101MB21025AB8F174E665B6D53EFADFD99@CY4PR1101MB2102.namprd11.prod.outlook.com> (raw)

Signed-off-by: Jakub Grajciar jgrajcia@cisco.com<mailto:jgrajcia@cisco.com>
---
 doc/guides/rel_notes/release_21_11.rst | 3 +++
 lib/eal/include/rte_eal_memconfig.h    | 4 ----
 lib/eal/version.map                    | 4 +---
 3 files changed, 4 insertions(+), 7 deletions(-)

diff --git a/doc/guides/rel_notes/release_21_11.rst b/doc/guides/rel_notes/release_21_11.rst
index 675b573834..1611562f6a 100644
--- a/doc/guides/rel_notes/release_21_11.rst
+++ b/doc/guides/rel_notes/release_21_11.rst
@@ -107,6 +107,9 @@ ABI Changes
    Also, make sure to start the actual text at the margin.
    =======================================================

+* The experimental function ``rte_mcfg_get_single_file_segments`` has been
+  promoted to stable ABI.
+

 Known Issues
 ------------
diff --git a/lib/eal/include/rte_eal_memconfig.h b/lib/eal/include/rte_eal_memconfig.h
index dede2ee324..d61023d80a 100644
--- a/lib/eal/include/rte_eal_memconfig.h
+++ b/lib/eal/include/rte_eal_memconfig.h
@@ -112,13 +112,9 @@ 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 beeb986adc..0cb757a1cf 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -121,6 +121,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;
@@ -328,9 +329,6 @@ EXPERIMENTAL {
    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



             reply	other threads:[~2021-09-13  8:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13  8:44 Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco) [this message]
2021-09-28 19:39 ` 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=CY4PR1101MB21025AB8F174E665B6D53EFADFD99@CY4PR1101MB2102.namprd11.prod.outlook.com \
    --to=jgrajcia@cisco.com \
    --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).