DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ciara Loftus <ciara.loftus@intel.com>
To: dev@dpdk.org
Cc: Ciara Loftus <ciara.loftus@intel.com>
Subject: [PATCH v2 5/5] doc: remove deprecation notice of SSE in some Intel drivers
Date: Wed, 17 Dec 2025 14:32:23 +0000	[thread overview]
Message-ID: <20251217143223.3208830-6-ciara.loftus@intel.com> (raw)
In-Reply-To: <20251217143223.3208830-1-ciara.loftus@intel.com>

The SSE paths in the i40e, iavf and ice Intel drivers have been
removed, so this deprecation notice is no longer required.

Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
---
 doc/guides/rel_notes/deprecation.rst | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 8653d6ca03..ac667e91a6 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -139,11 +139,3 @@ Deprecation Notices
 * bus/vmbus: Starting DPDK 25.11, all the vmbus API defined in
   ``drivers/bus/vmbus/rte_bus_vmbus.h`` will become internal to DPDK.
   Those API functions are used internally by DPDK core and netvsc PMD.
-
-* 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.
-- 
2.43.0


      parent reply	other threads:[~2025-12-17 14:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 12:35 [PATCH 0/4] Remove SSE from " Ciara Loftus
2025-08-25 12:35 ` [PATCH 1/4] net/i40e: remove SSE vector path Ciara Loftus
2025-08-25 12:35 ` [PATCH 2/4] net/iavf: " Ciara Loftus
2025-08-25 12:35 ` [PATCH 3/4] net/ice: " Ciara Loftus
2025-08-26  7:31   ` Khadem Ullah
2025-08-26  7:54     ` Bruce Richardson
2025-08-26  9:29       ` Khadem Ullah
2025-08-26 10:50         ` Bruce Richardson
2025-08-26 11:54           ` Khadem Ullah
2025-08-26 12:05             ` Bruce Richardson
2025-08-26 12:38               ` Khadem Ullah
2025-08-26 12:02           ` Khadem Ullah
2025-08-25 12:35 ` [PATCH 4/4] doc: add release note entry for SSE removal Ciara Loftus
2025-08-25 13:20   ` Bruce Richardson
2025-12-11 12:25 ` [PATCH 0/4] Remove SSE from some Intel drivers Bruce Richardson
2025-12-17 14:32 ` [PATCH v2 0/5] Remove SSE Rx/Tx paths " Ciara Loftus
2025-12-17 14:32   ` [PATCH v2 1/5] net/i40e: remove SSE vector path Ciara Loftus
2025-12-17 14:32   ` [PATCH v2 2/5] net/iavf: " Ciara Loftus
2025-12-17 14:32   ` [PATCH v2 3/5] net/ice: " Ciara Loftus
2025-12-17 14:32   ` [PATCH v2 4/5] doc: add release note entry for SSE removal Ciara Loftus
2025-12-17 14:32   ` Ciara Loftus [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=20251217143223.3208830-6-ciara.loftus@intel.com \
    --to=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).