DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Gavin Li <gavinl@nvidia.com>,
	matan@nvidia.com, viacheslavo@nvidia.com, orika@nvidia.com,
	thomas@monjalon.net
Cc: dev@dpdk.org, rasland@nvidia.com
Subject: Re: [V1] doc: announce deprecation of flow item VXLAN-GPE
Date: Fri, 26 Jul 2024 12:31:06 +0100	[thread overview]
Message-ID: <28be443d-928e-4156-904a-dccb138a6e5f@amd.com> (raw)
In-Reply-To: <20240726085157.197651-1-gavinl@nvidia.com>

On 7/26/2024 9:51 AM, Gavin Li wrote:
> Adding the deprecation notice as reminder for removing
> RTE_FLOW_ITEM_TYPE_VXLAN_GPE and its related structures,
> eg. rte_vxlan_gpe_hdr, rte_flow_item_vxlan_gpe, etc.
> 
> The proposed time of the removal is DPDK release 25.11.
> 
> Signed-off-by: Gavin Li <gavinl@nvidia.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 6948641ff6..5c04f88557 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -115,6 +115,13 @@ Deprecation Notices
>    The legacy actions should be removed
>    once ``MODIFY_FIELD`` alternative is implemented in drivers.
>  
> + * ethdev,net: The flow item ``RTE_FLOW_ITEM_TYPE_VXLAN_GPE`` is replaced with ``RTE_FLOW_ITEM_TYPE_VXLAN``.
> +   The struct ``rte_flow_item_vxlan_gpe``, its mask ``rte_flow_item_vxlan_gpe_mask`` are replaced with
> +   ``rte_flow_item_vxlan and its mask`` and its mask ``rte_flow_item_vxlan_mask``.
> +   The item ``RTE_FLOW_ITEM_TYPE_VXLAN_GPE``, the struct ``rte_flow_item_vxlan_gpe``, its mask ``rte_flow_item_vxlan_gpe_mask``,
> +   and the header struct ``rte_vxlan_gpe_hdr`` with the macro ``RTE_ETHER_VXLAN_GPE_HLEN``
> +   will be removed in DPDK 25.11.
> +
>  * cryptodev: The function ``rte_cryptodev_cb_fn`` will be updated
>    to have another parameter ``qp_id`` to return the queue pair ID
>    which got error interrupt to the application,
>

Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>

  reply	other threads:[~2024-07-26 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26  8:51 Gavin Li
2024-07-26 11:31 ` Ferruh Yigit [this message]
2024-07-29  8:48   ` Thomas Monjalon
2024-07-29 13:47     ` Ajit Khaparde
2024-07-31 10:33       ` Thomas Monjalon

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=28be443d-928e-4156-904a-dccb138a6e5f@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=gavinl@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).