From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Jerin Jacob <jerinj@marvell.com>
Subject: [PATCH v4 10/16] eventdev: add allocation function attributes
Date: Fri, 24 Jan 2025 10:15:01 -0800 [thread overview]
Message-ID: <20250124181704.86567-11-stephen@networkplumber.org> (raw)
In-Reply-To: <20250124181704.86567-1-stephen@networkplumber.org>
Use function attributes to catch cases where eventdev is allocated
but not freed correctly.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/eventdev/rte_event_ring.h | 27 ++++++++++++++-------------
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/lib/eventdev/rte_event_ring.h b/lib/eventdev/rte_event_ring.h
index 5769da269e..a8f308e4d6 100644
--- a/lib/eventdev/rte_event_ring.h
+++ b/lib/eventdev/rte_event_ring.h
@@ -247,7 +247,18 @@ int
rte_event_ring_init(struct rte_event_ring *r, const char *name,
unsigned int count, unsigned int flags);
-/*
+
+/**
+ * De-allocate all memory used by the ring.
+ *
+ * @param r
+ * Pointer to ring to created with rte_event_ring_create().
+ * If r is NULL, no operation is performed.
+ */
+void
+rte_event_ring_free(struct rte_event_ring *r);
+
+/**
* Create an event ring structure
*
* This function allocates memory and initializes an event ring inside that
@@ -288,8 +299,8 @@ rte_event_ring_init(struct rte_event_ring *r, const char *name,
* - ENOMEM - no appropriate memory area found in which to create memzone
*/
struct rte_event_ring *
-rte_event_ring_create(const char *name, unsigned int count, int socket_id,
- unsigned int flags);
+rte_event_ring_create(const char *name, unsigned int count, int socket_id, unsigned int flags)
+ __rte_malloc __rte_dealloc(rte_event_ring_free, 1);
/**
* Search for an event ring based on its name
@@ -304,16 +315,6 @@ rte_event_ring_create(const char *name, unsigned int count, int socket_id,
struct rte_event_ring *
rte_event_ring_lookup(const char *name);
-/**
- * De-allocate all memory used by the ring.
- *
- * @param r
- * Pointer to ring to created with rte_event_ring_create().
- * If r is NULL, no operation is performed.
- */
-void
-rte_event_ring_free(struct rte_event_ring *r);
-
/**
* Return the size of the event ring.
*
--
2.45.2
next prev parent reply other threads:[~2025-01-24 18:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250110170603.538756-1-stephen@networkplumber.or>
2025-01-20 23:23 ` [PATCH v2 0/3] Fix warnings when using gcc 15 Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 1/3] crypto/cnxk: fix gcc 15 warning Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 2/3] net/thunderx/base: fix build with Gcc 15 Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 3/3] examples/flow_filtering: fix gcc 15 overflow warning Stephen Hemminger
2025-01-22 10:50 ` [PATCH v2 0/3] Fix warnings when using gcc 15 David Marchand
2025-01-23 16:28 ` [PATCH v3 00/15] Add attributes to allocation functions Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 01/15] fib: add allocation function attributes Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 02/15] rib: annotate rib allocation functions Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 03/15] hash: add allocation function attributes Stephen Hemminger
2025-01-24 8:37 ` Konstantin Ananyev
2025-01-23 16:28 ` [PATCH v3 04/15] lpm: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 05/15] pipeline: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 06/15] acl: " Stephen Hemminger
2025-01-24 8:36 ` Konstantin Ananyev
2025-01-23 16:28 ` [PATCH v3 07/15] bitratestats: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 08/15] member: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 09/15] mempool: " Stephen Hemminger
2025-01-24 8:32 ` Konstantin Ananyev
2025-01-23 16:28 ` [PATCH v3 10/15] eventdev: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 11/15] ring: " Stephen Hemminger
2025-01-24 8:31 ` Konstantin Ananyev
2025-01-23 16:28 ` [PATCH v3 12/15] reorder: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 13/15] compressdev: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 14/15] telemetry: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 15/15] sched: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 00/16] Add " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 01/16] fib: add " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 02/16] rib: annotate rib allocation functions Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 03/16] hash: add allocation function attributes Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 04/16] lpm: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 05/16] pipeline: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 06/16] acl: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 07/16] bitratestats: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 08/16] member: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 09/16] mempool: " Stephen Hemminger
2025-01-24 18:15 ` Stephen Hemminger [this message]
2025-01-24 18:15 ` [PATCH v4 11/16] ring: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 12/16] reorder: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 13/16] compressdev: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 14/16] telemetry: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 15/16] sched: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 16/16] doc: add release note about allocation attributes Stephen Hemminger
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=20250124181704.86567-11-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
/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).