DPDK patches and discussions
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Yipeng Wang <yipeng1.wang@intel.com>,
	Sameh Gobriel <sameh.gobriel@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: RE: [PATCH v3 03/15] hash: add allocation function attributes
Date: Fri, 24 Jan 2025 08:37:30 +0000	[thread overview]
Message-ID: <59e97d2ca1f6483bb9ea006f5cdfb5a7@huawei.com> (raw)
In-Reply-To: <20250123163003.23394-4-stephen@networkplumber.org>



> Use function attributes to catch cases where hash table is allocated
> but not freed correctly.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  lib/hash/rte_fbk_hash.h | 24 +++++++++++++-----------
>  lib/hash/rte_hash.h     | 21 +++++++++++----------
>  2 files changed, 24 insertions(+), 21 deletions(-)
> 
> diff --git a/lib/hash/rte_fbk_hash.h b/lib/hash/rte_fbk_hash.h
> index 1f0c1d1b6c..b1a43f37b4 100644
> --- a/lib/hash/rte_fbk_hash.h
> +++ b/lib/hash/rte_fbk_hash.h
> @@ -322,6 +322,16 @@ rte_fbk_hash_get_load_factor(struct rte_fbk_hash_table *ht)
>   */
>  struct rte_fbk_hash_table *rte_fbk_hash_find_existing(const char *name);
> 
> +
> +/**
> + * Free all memory used by a hash table.
> + * Has no effect on hash tables allocated in memory zones
> + *
> + * @param ht
> + *   Hash table to deallocate.
> + */
> +void rte_fbk_hash_free(struct rte_fbk_hash_table *ht);
> +
>  /**
>   * Create a new hash table for use with four byte keys.
>   *
> @@ -339,17 +349,9 @@ struct rte_fbk_hash_table *rte_fbk_hash_find_existing(const char *name);
>   *    - EEXIST - a memzone with the same name already exists
>   *    - ENOMEM - no appropriate memory area found in which to create memzone
>   */
> -struct rte_fbk_hash_table * \
> -rte_fbk_hash_create(const struct rte_fbk_hash_params *params);
> -
> -/**
> - * Free all memory used by a hash table.
> - * Has no effect on hash tables allocated in memory zones
> - *
> - * @param ht
> - *   Hash table to deallocate.
> - */
> -void rte_fbk_hash_free(struct rte_fbk_hash_table *ht);
> +struct rte_fbk_hash_table *
> +rte_fbk_hash_create(const struct rte_fbk_hash_params *params)
> +	__rte_malloc __rte_dealloc(rte_fbk_hash_free, 1);
> 
>  #ifdef __cplusplus
>  }
> diff --git a/lib/hash/rte_hash.h b/lib/hash/rte_hash.h
> index 05ab447e4a..736fb15885 100644
> --- a/lib/hash/rte_hash.h
> +++ b/lib/hash/rte_hash.h
> @@ -125,6 +125,15 @@ struct rte_hash_rcu_config {
>  /** @internal A hash table structure. */
>  struct rte_hash;
> 
> +/**
> + * De-allocate all memory used by hash table.
> + *
> + * @param h
> + *   Hash table to free, if NULL, the function does nothing.
> + */
> +void
> +rte_hash_free(struct rte_hash *h);
> +
>  /**
>   * Create a new hash table.
>   *
> @@ -143,7 +152,8 @@ struct rte_hash;
>   *    - ENOMEM - no appropriate memory area found in which to create memzone
>   */
>  struct rte_hash *
> -rte_hash_create(const struct rte_hash_parameters *params);
> +rte_hash_create(const struct rte_hash_parameters *params)
> +	__rte_malloc __rte_dealloc(rte_hash_free, 1);
> 
>  /**
>   * Set a new hash compare function other than the default one.
> @@ -171,15 +181,6 @@ void rte_hash_set_cmp_func(struct rte_hash *h, rte_hash_cmp_eq_t func);
>  struct rte_hash *
>  rte_hash_find_existing(const char *name);
> 
> -/**
> - * De-allocate all memory used by hash table.
> - *
> - * @param h
> - *   Hash table to free, if NULL, the function does nothing.
> - */
> -void
> -rte_hash_free(struct rte_hash *h);
> -
>  /**
>   * Reset all hash structure, by zeroing all entries.
>   * When RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF is enabled,
> --

Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>

> 2.45.2


  reply	other threads:[~2025-01-24  8:37 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 [this message]
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   ` [PATCH v4 10/16] eventdev: " Stephen Hemminger
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=59e97d2ca1f6483bb9ea006f5cdfb5a7@huawei.com \
    --to=konstantin.ananyev@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=sameh.gobriel@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=vladimir.medvedkin@intel.com \
    --cc=yipeng1.wang@intel.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).