All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: Re: [PATCH 05/20] eal: promote lcore variables API to stable
Date: Thu, 8 Oct 2026 11:04:08 +0100	[thread overview]
Message-ID: <asdqmG7cN3lpgJu3@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20261007214115.3092715-6-stephen@networkplumber.org>

On Wed, Oct 07, 2026 at 02:39:35PM -0700, Stephen Hemminger wrote:
> rte_lcore_var_alloc() was added in 24.11 and has not changed. The
> RTE_LCORE_VAR_* macros that form the public interface were never marked
> experimental, so the header carried a file level warning while the
> macros applications actually use looked stable.
> 
> The API is used by rte_random, rte_service, the x86 power intrinsics and
> the power PMD management code. Promote the allocator and drop the file
> level warning.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

See comment inline below though.

>  doc/guides/rel_notes/release_26_11.rst | 4 ++++
>  lib/eal/common/eal_common_lcore_var.c  | 2 +-
>  lib/eal/include/rte_lcore_var.h        | 3 ---
>  3 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/doc/guides/rel_notes/release_26_11.rst b/doc/guides/rel_notes/release_26_11.rst
> index 934efaaf93..62e7df5728 100644
> --- a/doc/guides/rel_notes/release_26_11.rst
> +++ b/doc/guides/rel_notes/release_26_11.rst
> @@ -240,6 +240,10 @@ API Changes
>    are now declared with an alignment of 1 on all architectures.
>    The compiler may generate narrower loads and stores than before.
>  
> +* eal: Promoted ``rte_memzero_explicit``, ``rte_free_sensitive``,
> +  ``rte_basename``, ``rte_size_to_str`` and the lcore variables API
> +  from experimental to stable.
> +
>  * ethdev: Updated VMDq related API.
>  

This would be better done as a bulleted list so it can be easily added to
by patches. Patch 2 of this set should start by adding to release note:

* Promoted the following APIs to stable:
  - ``rte_basename`` in EAL

with the later patches adding a new bullet each time.

>    * At port configuration time, the number of VMDq pools advertised by a driver
> diff --git a/lib/eal/common/eal_common_lcore_var.c b/lib/eal/common/eal_common_lcore_var.c
> index 8a7920ed0f..a2af0e19d8 100644
> --- a/lib/eal/common/eal_common_lcore_var.c
> +++ b/lib/eal/common/eal_common_lcore_var.c
> @@ -76,7 +76,7 @@ lcore_var_alloc(size_t size, size_t align)
>  	return handle;
>  }
>  
> -RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_lcore_var_alloc, 24.11)
> +RTE_EXPORT_SYMBOL(rte_lcore_var_alloc)
>  void *
>  rte_lcore_var_alloc(size_t size, size_t align)
>  {
> diff --git a/lib/eal/include/rte_lcore_var.h b/lib/eal/include/rte_lcore_var.h
> index 48b022e84e..2737ae947b 100644
> --- a/lib/eal/include/rte_lcore_var.h
> +++ b/lib/eal/include/rte_lcore_var.h
> @@ -15,8 +15,6 @@
>   *
>   * Please refer to the lcore variables' programmer's guide
>   * for an overview of this API and its implementation.
> - *
> - * EXPERIMENTAL: this API may change, or be removed, without prior notice.
>   */
>  
>  #include <stddef.h>
> @@ -199,7 +197,6 @@ rte_lcore_var_lcore(unsigned int lcore_id, void *handle)
>   *   The variable's handle, stored in a void pointer value.
>   *   The value is always non-NULL.
>   */
> -__rte_experimental
>  void *
>  rte_lcore_var_alloc(size_t size, size_t align)
>  	__rte_alloc_align(2);
> -- 
> 2.53.0
> 

  reply	other threads:[~2026-10-08 10:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 21:39 [PATCH 00/20] promote long standing experimental API to stable Stephen Hemminger
2026-10-07 21:39 ` [PATCH 01/20] eal: add missing export for rte_basename Stephen Hemminger
2026-10-08  9:56   ` Bruce Richardson
2026-10-07 21:39 ` [PATCH 02/20] eal: promote rte_basename to stable Stephen Hemminger
2026-10-08  9:56   ` Bruce Richardson
2026-10-07 21:39 ` [PATCH 03/20] eal: promote explicit zero and sensitive free " Stephen Hemminger
2026-10-08 10:01   ` Bruce Richardson
2026-10-07 21:39 ` [PATCH 04/20] eal: promote rte_size_to_str " Stephen Hemminger
2026-10-08 10:01   ` Bruce Richardson
2026-10-07 21:39 ` [PATCH 05/20] eal: promote lcore variables API " Stephen Hemminger
2026-10-08 10:04   ` Bruce Richardson [this message]
2026-10-07 21:39 ` [PATCH 06/20] cmdline: promote bool token ops " Stephen Hemminger
2026-10-08 10:05   ` Bruce Richardson
2026-10-07 21:39 ` [PATCH 07/20] ethdev: promote link connector to string " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 08/20] port: promote SWX port API " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 09/20] table: promote SWX table " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 10/20] pipeline: promote SWX IPsec " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 11/20] pipeline: promote SWX pipeline and control " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 12/20] power: promote PM QoS and uncore " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 13/20] ring: promote soring " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 14/20] dispatcher: promote " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 15/20] argparse: " Stephen Hemminger
2026-10-08 10:15   ` Bruce Richardson
2026-10-07 21:39 ` [PATCH 16/20] node: " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 17/20] hash: promote RCU reclaim and thash key generation " Stephen Hemminger
2026-10-08 10:16   ` Bruce Richardson
2026-10-07 21:39 ` [PATCH 18/20] cryptodev: promote algorithm helpers " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 19/20] pdcp: promote API " Stephen Hemminger
2026-10-07 21:39 ` [PATCH 20/20] mempool: promote memory range and alignment " Stephen Hemminger
2026-10-08  7:19   ` Morten Brørup

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=asdqmG7cN3lpgJu3@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.