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>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: [PATCH v5 15/16] sched: add allocation function attributes
Date: Fri, 24 Jan 2025 18:11:28 -0800	[thread overview]
Message-ID: <20250125021305.76485-16-stephen@networkplumber.org> (raw)
In-Reply-To: <20250125021305.76485-1-stephen@networkplumber.org>

Use function attributes to catch cases where sched port config
is allocated but not freed correctly.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 lib/sched/rte_sched.h | 24 ++++++++++++++----------
 1 file changed, 14 insertions(+), 10 deletions(-)

diff --git a/lib/sched/rte_sched.h b/lib/sched/rte_sched.h
index 222e6b3583..e98f43072d 100644
--- a/lib/sched/rte_sched.h
+++ b/lib/sched/rte_sched.h
@@ -51,6 +51,7 @@
  *	    queues within same pipe lowest priority traffic class (best-effort).
  */
 
+#include <rte_common.h>
 #include <rte_mbuf.h>
 #include <rte_meter.h>
 
@@ -310,16 +311,7 @@ struct rte_sched_port_params {
  * Configuration
  */
 
-/**
- * Hierarchical scheduler port configuration
- *
- * @param params
- *   Port scheduler configuration parameter structure
- * @return
- *   Handle to port scheduler instance upon success or NULL otherwise.
- */
-struct rte_sched_port *
-rte_sched_port_config(struct rte_sched_port_params *params);
+struct rte_sched_port;
 
 /**
  * Hierarchical scheduler port free
@@ -331,6 +323,18 @@ rte_sched_port_config(struct rte_sched_port_params *params);
 void
 rte_sched_port_free(struct rte_sched_port *port);
 
+/**
+ * Hierarchical scheduler port configuration
+ *
+ * @param params
+ *   Port scheduler configuration parameter structure
+ * @return
+ *   Handle to port scheduler instance upon success or NULL otherwise.
+ */
+struct rte_sched_port *
+rte_sched_port_config(struct rte_sched_port_params *params)
+	__rte_malloc __rte_dealloc(rte_sched_port_free, 1);
+
 /**
  * Hierarchical scheduler pipe profile add
  *
-- 
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   ` [PATCH v5 10/16] eventdev: " Stephen Hemminger
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   ` Stephen Hemminger [this message]
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-16-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=cristian.dumitrescu@intel.com \
    --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).