DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org, Ray Kinsella <mdr@ashroe.eu>
Subject: [dpdk-dev] [PATCH v1 1/7] eal: promote IPC API's to stable
Date: Fri, 10 Sep 2021 12:30:03 +0000	[thread overview]
Message-ID: <029012e59f555be16bed829229e8b48016157371.1631277001.git.anatoly.burakov@intel.com> (raw)

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.h | 24 ------------------------
 lib/eal/version.map       | 14 ++++++--------
 2 files changed, 6 insertions(+), 32 deletions(-)

diff --git a/lib/eal/include/rte_eal.h b/lib/eal/include/rte_eal.h
index eaf6469e50..f1af86bfff 100644
--- a/lib/eal/include/rte_eal.h
+++ b/lib/eal/include/rte_eal.h
@@ -209,9 +209,6 @@ typedef int (*rte_mp_async_reply_t)(const struct rte_mp_msg *request,
 		const struct rte_mp_reply *reply);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Register an action function for primary/secondary communication.
  *
  * Call this function to register an action, if the calling component wants
@@ -231,14 +228,10 @@ typedef int (*rte_mp_async_reply_t)(const struct rte_mp_msg *request,
  *  - 0 on success.
  *  - (<0) on failure.
  */
-__rte_experimental
 int
 rte_mp_action_register(const char *name, rte_mp_t action);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Unregister an action function for primary/secondary communication.
  *
  * Call this function to unregister an action  if the calling component does
@@ -252,14 +245,10 @@ rte_mp_action_register(const char *name, rte_mp_t action);
  *   The name argument plays as the nonredundant key to find the action.
  *
  */
-__rte_experimental
 void
 rte_mp_action_unregister(const char *name);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Send a message to the peer process.
  *
  * This function will send a message which will be responded by the action
@@ -272,14 +261,10 @@ rte_mp_action_unregister(const char *name);
  *  - On success, return 0.
  *  - On failure, return -1, and the reason will be stored in rte_errno.
  */
-__rte_experimental
 int
 rte_mp_sendmsg(struct rte_mp_msg *msg);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Send a request to the peer process and expect a reply.
  *
  * This function sends a request message to the peer process, and will
@@ -307,15 +292,11 @@ rte_mp_sendmsg(struct rte_mp_msg *msg);
  *  - On success, return 0.
  *  - On failure, return -1, and the reason will be stored in rte_errno.
  */
-__rte_experimental
 int
 rte_mp_request_sync(struct rte_mp_msg *req, struct rte_mp_reply *reply,
 	       const struct timespec *ts);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Send a request to the peer process and expect a reply in a separate callback.
  *
  * This function sends a request message to the peer process, and will not
@@ -337,15 +318,11 @@ rte_mp_request_sync(struct rte_mp_msg *req, struct rte_mp_reply *reply,
  *  - On success, return 0.
  *  - On failure, return -1, and the reason will be stored in rte_errno.
  */
-__rte_experimental
 int
 rte_mp_request_async(struct rte_mp_msg *req, const struct timespec *ts,
 		rte_mp_async_reply_t clb);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Send a reply to the peer process.
  *
  * This function will send a reply message in response to a request message
@@ -366,7 +343,6 @@ rte_mp_request_async(struct rte_mp_msg *req, const struct timespec *ts,
  *  - On success, return 0.
  *  - On failure, return -1, and the reason will be stored in rte_errno.
  */
-__rte_experimental
 int
 rte_mp_reply(struct rte_mp_msg *msg, const char *peer);
 
diff --git a/lib/eal/version.map b/lib/eal/version.map
index beeb986adc..c6e78d68d1 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -146,6 +146,12 @@ DPDK_22 {
 	rte_memzone_reserve_aligned;
 	rte_memzone_reserve_bounded;
 	rte_memzone_walk;
+	rte_mp_action_register;
+	rte_mp_action_unregister;
+	rte_mp_reply;
+	rte_mp_request_async;
+	rte_mp_request_sync;
+	rte_mp_sendmsg;
 	rte_openlog_stream;
 	rte_rand;
 	rte_realloc;
@@ -224,12 +230,6 @@ DPDK_22 {
 EXPERIMENTAL {
 	global:
 
-	# added in 18.02
-	rte_mp_action_register;
-	rte_mp_action_unregister;
-	rte_mp_reply;
-	rte_mp_sendmsg;
-
 	# added in 18.05
 	rte_dev_event_callback_register;
 	rte_dev_event_callback_unregister;
@@ -264,8 +264,6 @@ EXPERIMENTAL {
 	rte_memseg_contig_walk;
 	rte_memseg_list_walk;
 	rte_memseg_walk;
-	rte_mp_request_async;
-	rte_mp_request_sync;
 
 	# added in 18.08
 	rte_class_find;
-- 
2.25.1


             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 Anatoly Burakov [this message]
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 ` [dpdk-dev] [PATCH v1 7/7] eal: promote mcfg " Anatoly Burakov
2021-09-10 16:23   ` 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=029012e59f555be16bed829229e8b48016157371.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).