From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 08/15] eal: make pflock API stable
Date: Wed, 9 Aug 2023 09:43:00 -0700 [thread overview]
Message-ID: <20230809164312.308093-9-stephen@networkplumber.org> (raw)
In-Reply-To: <20230809164312.308093-1-stephen@networkplumber.org>
Added in 21.11 release.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/eal/include/rte_pflock.h | 20 --------------------
1 file changed, 20 deletions(-)
diff --git a/lib/eal/include/rte_pflock.h b/lib/eal/include/rte_pflock.h
index a3f7291fa1f0..a751a7d8add9 100644
--- a/lib/eal/include/rte_pflock.h
+++ b/lib/eal/include/rte_pflock.h
@@ -79,15 +79,11 @@ typedef struct rte_pflock rte_pflock_t;
#define RTE_PFLOCK_INITIALIZER { }
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Initialize the pflock to an unlocked state.
*
* @param pf
* A pointer to the pflock.
*/
-__rte_experimental
static inline void
rte_pflock_init(struct rte_pflock *pf)
{
@@ -98,15 +94,11 @@ rte_pflock_init(struct rte_pflock *pf)
}
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Take a pflock for read.
*
* @param pf
* A pointer to a pflock structure.
*/
-__rte_experimental
static inline void
rte_pflock_read_lock(rte_pflock_t *pf)
{
@@ -127,15 +119,11 @@ rte_pflock_read_lock(rte_pflock_t *pf)
}
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Release a pflock locked for reading.
*
* @param pf
* A pointer to the pflock structure.
*/
-__rte_experimental
static inline void
rte_pflock_read_unlock(rte_pflock_t *pf)
{
@@ -143,15 +131,11 @@ rte_pflock_read_unlock(rte_pflock_t *pf)
}
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Take the pflock for write.
*
* @param pf
* A pointer to the pflock structure.
*/
-__rte_experimental
static inline void
rte_pflock_write_lock(rte_pflock_t *pf)
{
@@ -179,15 +163,11 @@ rte_pflock_write_lock(rte_pflock_t *pf)
}
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Release a pflock held for writing.
*
* @param pf
* A pointer to a pflock structure.
*/
-__rte_experimental
static inline void
rte_pflock_write_unlock(rte_pflock_t *pf)
{
--
2.39.2
next prev parent reply other threads:[~2023-08-09 16:45 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 16:42 [PATCH 00/15] eal: mark older API's stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 01/15] eal: make bitops a stable API Stephen Hemminger
2023-08-09 17:58 ` Tyler Retzlaff
2023-08-09 20:07 ` Stephen Hemminger
2023-08-09 21:59 ` Tyler Retzlaff
2023-08-09 16:42 ` [PATCH 02/15] eal: mark rte_dev API's as stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 03/15] eal: make rte_class API's stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 04/15] eal: make rte_version_XXX " Stephen Hemminger
2023-08-10 8:24 ` Bruce Richardson
2023-08-09 16:42 ` [PATCH 05/15] eal: make rte_drand a stable API Stephen Hemminger
2023-08-09 16:42 ` [PATCH 06/15] eal: make rte_service_lcore_may_be_active stable Stephen Hemminger
2023-08-10 9:08 ` Van Haaren, Harry
2023-08-09 16:42 ` [PATCH 07/15] eal: make rte_devargs_reset stable Stephen Hemminger
2023-08-09 16:43 ` Stephen Hemminger [this message]
2023-08-09 16:43 ` [PATCH 09/15] eal: make seqcount and seqlock stable Stephen Hemminger
2023-08-09 19:47 ` Mattias Rönnblom
2023-08-09 16:43 ` [PATCH 10/15] eal: mark rte_intr_XXX API's as stable Stephen Hemminger
2023-08-09 16:43 ` [PATCH 11/15] eal: mark rte_atomic128_cmp_exchange " Stephen Hemminger
2023-08-09 17:50 ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 12/15] eal: make most rte_thread API's stable Stephen Hemminger
2023-08-09 17:53 ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 13/15] eal: mark rte_power " Stephen Hemminger
2023-08-09 16:43 ` [PATCH 14/15] eal: mark rte_eal_vfio_get_token stable Stephen Hemminger
2023-08-09 17:55 ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 15/15] eal: mark rte_vect simd bandwidth API as stable Stephen Hemminger
2023-10-18 19:29 ` [PATCH 00/15] eal: mark older API's stable David Marchand
2023-10-20 21:41 ` [PATCH v2 00/14] eal: mark older API's as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 01/14] eal: make bitops a stable API Stephen Hemminger
2023-10-23 2:31 ` Joyce Kong
2023-10-20 21:41 ` [PATCH v2 02/14] eal: mark rte_dev API's as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 03/14] eal: make rte_class API's stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 04/14] eal: make rte_drand a stable API Stephen Hemminger
2023-10-23 16:12 ` Mattias Rönnblom
2023-10-20 21:41 ` [PATCH v2 05/14] eal: make rte_service_lcore_may_be_active stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 06/14] eal: make rte_devargs_reset stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 07/14] eal: make pflock API stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 08/14] eal: make seqcount and seqlock stable Stephen Hemminger
2023-10-23 16:14 ` Mattias Rönnblom
2023-10-20 21:41 ` [PATCH v2 09/14] eal: mark rte_intr_XXX API's as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 10/14] eal: mark rte_atomic128_cmp_exchange " Stephen Hemminger
2023-10-23 3:00 ` Ruifeng Wang
2023-10-20 21:41 ` [PATCH v2 11/14] eal: mark rte_power API's stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 12/14] eal: mark rte_eal_vfio_get_token stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 13/14] eal: mark rte_vect simd bandwidth API as stable Stephen Hemminger
2023-10-20 21:41 ` [PATCH v2 14/14] eal: make rte_version API's stable Stephen Hemminger
2023-10-23 9:13 ` [PATCH v2 00/14] eal: mark older API's as stable Bruce Richardson
2023-11-14 13: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=20230809164312.308093-9-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--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).