DPDK patches and discussions
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: Ciara Loftus <ciara.loftus@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>
Subject: RE: [PATCH v2] net/intel: deprecate some SSE paths
Date: Tue, 15 Jul 2025 15:14:32 +0000	[thread overview]
Message-ID: <1e42646f1362423981eef0ae0efb34b9@huawei.com> (raw)
In-Reply-To: <20250703143119.1140097-1-ciara.loftus@intel.com>



> The SSE rx and tx paths will be removed from the i40e, iavf and ice
> drivers in the 25.11 release. Each of these drivers have faster vector
> paths (AVX2 and AVX-512) which have feature parity with the soon to be
> removed SSE paths. In environments where AVX2 or AVX-512 are not
> supported, the scalar path will still be used, which also has feature
> parity.
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.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 e2d4125308..0d020c9c1f 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -80,6 +80,13 @@ Deprecation Notices
>    and the header struct ``rte_vxlan_gpe_hdr`` with the macro ``RTE_ETHER_VXLAN_GPE_HLEN``
>    will be removed in DPDK 25.11.
> 
> +* net/intel: drivers that have an SSE vector path alongside other vector paths,
> +  namely i40e, iavf and ice, will have their SSE vector paths removed in DPDK 25.11.
> +  Modern x86 systems all support AVX2, if not AVX-512, so the SSE path is no longer
> +  widely used. This change will not result in any feature loss, as the fallback
> +  scalar paths which have feature parity with SSE will be used in the cases where
> +  the SSE paths would have been used.
> +
>  * ethdev: The flow API matching pattern structures, ``struct rte_flow_item_*``,
>    should start with relevant protocol header structure from lib/net/.
>    The individual protocol header fields and the protocol header struct
> --

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

> 2.34.1


      parent reply	other threads:[~2025-07-15 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 12:16 [PATCH] " Ciara Loftus
2025-07-03 12:45 ` Bruce Richardson
2025-07-03 14:31 ` [PATCH v2] " Ciara Loftus
2025-07-15 14:13   ` Bruce Richardson
2025-07-15 15:14   ` Konstantin Ananyev [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=1e42646f1362423981eef0ae0efb34b9@huawei.com \
    --to=konstantin.ananyev@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.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 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).