DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Harman Kalra <hkalra@marvell.com>, Ray Kinsella <mdr@ashroe.eu>
Subject: [PATCH 3/4] eal: make some intr functions not experimental
Date: Wed, 16 Feb 2022 11:39:16 -0800	[thread overview]
Message-ID: <20220216193917.251657-4-stephen@networkplumber.org> (raw)
In-Reply-To: <20220216193917.251657-1-stephen@networkplumber.org>

These are functions related to interrupts that have been
in since 20.02 release or earlier.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 lib/eal/include/rte_interrupts.h | 12 +-----------
 lib/eal/version.map              | 10 +++-------
 2 files changed, 4 insertions(+), 18 deletions(-)

diff --git a/lib/eal/include/rte_interrupts.h b/lib/eal/include/rte_interrupts.h
index edbf0faeeffd..a378c0a0aa91 100644
--- a/lib/eal/include/rte_interrupts.h
+++ b/lib/eal/include/rte_interrupts.h
@@ -121,7 +121,6 @@ int rte_intr_callback_unregister(const struct rte_intr_handle *intr_handle,
  *  - On success, return the number of callback entities marked for remove.
  *  - On failure, a negative value.
  */
-__rte_experimental
 int
 rte_intr_callback_unregister_pending(const struct rte_intr_handle *intr_handle,
 				rte_intr_callback_fn cb_fn, void *cb_arg,
@@ -177,9 +176,6 @@ int rte_intr_enable(const struct rte_intr_handle *intr_handle);
 int rte_intr_disable(const struct rte_intr_handle *intr_handle);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * It acknowledges an interrupt raised for the specified handle.
  *
  * This function should be called at the end of each interrupt handler either
@@ -193,22 +189,16 @@ int rte_intr_disable(const struct rte_intr_handle *intr_handle);
  *  - On success, zero.
  *  - On failure, a negative value.
  */
-__rte_experimental
 int rte_intr_ack(const struct rte_intr_handle *intr_handle);
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
  * Check if currently executing in interrupt context
  *
  * @return
  *  - non zero in case of interrupt context
  *  - zero in case of process context
  */
-__rte_experimental
-int
-rte_thread_is_intr(void);
+int rte_thread_is_intr(void);
 
 /**
  * @warning
diff --git a/lib/eal/version.map b/lib/eal/version.map
index 18d46acfeb1e..131a0eea1f28 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -109,8 +109,10 @@ DPDK_22 {
 	rte_hexdump;
 	rte_hypervisor_get;
 	rte_hypervisor_get_name; # WINDOWS_NO_EXPORT
+	rte_intr_ack;
 	rte_intr_callback_register;
 	rte_intr_callback_unregister;
+	rte_intr_callback_unregister_pending;
 	rte_intr_disable;
 	rte_intr_enable;
 	rte_keepalive_create; # WINDOWS_NO_EXPORT
@@ -263,6 +265,7 @@ DPDK_22 {
 	rte_strsplit;
 	rte_sys_gettid;
 	rte_thread_get_affinity;
+	rte_thread_is_intr;
 	rte_thread_register;
 	rte_thread_set_affinity;
 	rte_thread_setname;
@@ -320,13 +323,6 @@ EXPERIMENTAL {
 	# added in 19.05
 	rte_dev_dma_map;
 	rte_dev_dma_unmap;
-	rte_intr_callback_unregister_pending;
-
-	# added in 19.08
-	rte_intr_ack;
-
-	# added in 20.02
-	rte_thread_is_intr;
 
 	# added in 20.05
 	__rte_eal_trace_alarm_cancel;
-- 
2.34.1


  parent reply	other threads:[~2022-02-16 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 19:39 [PATCH 0/4] eal: remove some experimental tags Stephen Hemminger
2022-02-16 19:39 ` [PATCH 1/4] rte_log: take of " Stephen Hemminger
2022-02-17 12:57   ` Ray Kinsella
2022-02-16 19:39 ` [PATCH 2/4] lcore: change rte_lcore_to_cpu_id and rte_lcore_cpuset as not experimental Stephen Hemminger
2022-02-17 12:55   ` Ray Kinsella
2022-02-16 19:39 ` Stephen Hemminger [this message]
2022-02-17 12:56   ` [PATCH 3/4] eal: make some intr functions " Ray Kinsella
2022-02-16 19:39 ` [PATCH 4/4] eal: mark rte_delay_us_sleep as " Stephen Hemminger
2022-02-17 12:56   ` Ray Kinsella
2022-06-26 15:34 ` [PATCH 0/4] eal: remove some experimental tags 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=20220216193917.251657-4-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --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).