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>,
	Jerin Jacob <jerinj@marvell.com>
Subject: [PATCH v5 10/16] eventdev: add allocation function attributes
Date: Fri, 24 Jan 2025 18:11:23 -0800	[thread overview]
Message-ID: <20250125021305.76485-11-stephen@networkplumber.org> (raw)
In-Reply-To: <20250125021305.76485-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


  parent reply	other threads:[~2025-01-25  2:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 17:06 [PATCH] crypto/cnxk: fix gcc 15 warning Stephen Hemminger
2025-01-25  2:11 ` [PATCH v5 00/16] Annotate allocation functions Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 01/16] fib: add allocation function attributes Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 02/16] rib: annotate rib allocation functions Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 03/16] hash: add allocation function attributes Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 04/16] lpm: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 05/16] pipeline: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 06/16] acl: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 07/16] bitratestats: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 08/16] member: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 09/16] mempool: " Stephen Hemminger
2025-01-25  2:11   ` Stephen Hemminger [this message]
2025-01-25  2:11   ` [PATCH v5 11/16] ring: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 12/16] reorder: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 13/16] compressdev: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 14/16] telemetry: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 15/16] sched: " Stephen Hemminger
2025-01-25  2:11   ` [PATCH v5 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=20250125021305.76485-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).