From: Stephen Hemminger <stephen@networkplumber.org>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: Ori Kam <orika@nvidia.com>, Thomas Monjalon <thomas@monjalon.net>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
<dev@dpdk.org>
Subject: Re: [PATCH v2] ethdev: promote flow metadata APIs to stable
Date: Sat, 30 May 2026 09:37:56 -0700 [thread overview]
Message-ID: <20260530093756.2aa1ad8b@phoenix.local> (raw)
In-Reply-To: <20260529072853.689683-1-dsosnowski@nvidia.com>
On Fri, 29 May 2026 09:28:53 +0200
Dariusz Sosnowski <dsosnowski@nvidia.com> wrote:
> Following experimental symbols related to flow metadata
> were added in v19.11:
>
> - rte_flow_dynf_metadata_register
> - rte_flow_dynf_metadata_offs
> - rte_flow_dynf_metadata_mask
>
> Type of rte_flow_dynf_metadata_offs was changed from int to int32_t
> in v20.05 release.
> There were no changes to these symbols since then.
>
> This patch promotes these symbols and removes __rte_experimental
> from the following inline functions:
>
> - rte_flow_dynf_metadata_avail
> - rte_flow_dynf_metadata_get
> - rte_flow_dynf_metadata_set
>
> All these symbols and functions will be used by netdev-doca
> backend in Open vSwitch [1].
> Stabilizing these symbols is required by current OVS policy
> to remove the need for ALLOW_EXPERIMENTAL_API [2].
>
> [1]: https://patchwork.ozlabs.org/project/openvswitch/list/?series=504726&state=%2A&archive=both
> [2]: https://mail.openvswitch.org/pipermail/ovs-dev/2026-May/432066.html
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
LGTM
Applied to next-net
prev parent reply other threads:[~2026-05-30 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 10:32 [PATCH] ethdev: promote flow metadata APIs to stable Dariusz Sosnowski
2026-05-29 7:28 ` [PATCH v2] " Dariusz Sosnowski
2026-05-30 16:37 ` Stephen Hemminger [this message]
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=20260530093756.2aa1ad8b@phoenix.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
/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