All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Cc: dev@dpdk.org, orika@nvidia.com, thomas@monjalon.net
Subject: Re: [PATCH] ethdev: add GENEVE encapsulation and decapsulation actions
Date: Thu, 13 Nov 2025 20:27:25 -0800	[thread overview]
Message-ID: <20251113202725.4aaefeee@phoenix> (raw)
In-Reply-To: <20251113102158.48040-1-sunyang.wu@jaguarmicro.com>

On Thu, 13 Nov 2025 18:21:58 +0800
Sunyang Wu <sunyang.wu@jaguarmicro.com> wrote:

> Add new flow action types for GENEVE tunnel manipulation:
> 
> 1. RTE_FLOW_ACTION_TYPE_GENEVE_ENCAP - For encapsulating packets into
> GENEVE tunnels
> 2. RTE_FLOW_ACTION_TYPE_GENEVE_DECAP - For decapsulating packets from
> GENEVE tunnels
> 3. struct rte_flow_action_geneve_encap - Data structure to define tunnel
> encapsulation parameters
> 
> These actions allow users to build more flexible network virtualization
> solutions using GENEVE tunnels as specified by RFC8926.
> 
> Signed-off-by: Sunyang Wu <sunyang.wu@jaguarmicro.com>
> ---
>  lib/ethdev/rte_flow.h | 50 +++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 50 insertions(+)
> 
> diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h
> index 3d2ccdeb92..fc03489511 100644
> --- a/lib/ethdev/rte_flow.h
> +++ b/lib/ethdev/rte_flow.h
> @@ -2825,6 +2825,23 @@ enum rte_flow_action_type {
>  	 */
>  	RTE_FLOW_ACTION_TYPE_NVGRE_DECAP,
>  
> +	/**
> +	 * Encapsulate flow in GENEVE tunnel defined in the
> +	 * rte_flow_action_geneve_encap action structure.
> +	 *
> +	 * See struct rte_flow_action_geneve_encap.
> +	 */
> +	RTE_FLOW_ACTION_TYPE_GENEVE_ENCAP,
> +
> +	/**
> +	 * Decapsulate outer most GENEVE tunnel from matched flow.
> +	 *
> +	 * If flow pattern does not define a valid GENEVE tunnel (as specified by
> +	 * RFC8296) then the PMD should return a RTE_FLOW_ERROR_TYPE_ACTION
> +	 * error.
> +	 */
> +	RTE_FLOW_ACTION_TYPE_GENEVE_DECAP,
> +
>  	/**
>  	 * Add outer header whose template is provided in its data buffer
>  	 *
> @@ -3738,6 +3755,39 @@ struct rte_flow_action_nvgre_encap {
>  	struct rte_flow_item *definition;
>  };
>  

It is too late to put a new feature like this into this release.
And if targeting next-release 26.03 the ABI is not allowed to change.
That means you will need to put the new flow actions at the end of the
enum rte_flow_action_type so that values don't get reordered.

Release Dates
-------------

The following are the proposed working dates for 25.11:

- Proposal deadline (RFC/v1 patches): 31 August 2025
- API freeze (-rc1): 24 October 2025
- PMD features freeze (-rc2): 7 November 2025
- Builtin applications features freeze (-rc3): 17 November 2025
- Release: 26 November 2025

See https://core.dpdk.org/roadmap/

      reply	other threads:[~2025-11-14  4:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 10:21 [PATCH] ethdev: add GENEVE encapsulation and decapsulation actions Sunyang Wu
2025-11-14  4:27 ` 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=20251113202725.4aaefeee@phoenix \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    --cc=sunyang.wu@jaguarmicro.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 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.