From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 4/4] doc: add release note entry for SSE removal
Date: Mon, 25 Aug 2025 14:20:14 +0100 [thread overview]
Message-ID: <aKxjDpR8d75HtxvW@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250825123548.1177090-5-ciara.loftus@intel.com>
On Mon, Aug 25, 2025 at 12:35:48PM +0000, Ciara Loftus wrote:
> The SSE paths have been removed from the i40e, iavf and ice Intel
> drivers. Add a release note documenting their removal.
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
> doc/guides/rel_notes/release_25_11.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_25_11.rst b/doc/guides/rel_notes/release_25_11.rst
> index ccad6d89ff..d2749f2e4b 100644
> --- a/doc/guides/rel_notes/release_25_11.rst
> +++ b/doc/guides/rel_notes/release_25_11.rst
> @@ -55,6 +55,11 @@ New Features
> Also, make sure to start the actual text at the margin.
> =======================================================
>
> +* **Removed the SSE vector paths from some Intel drivers.**
> +
> + The SSE path was not widely used, so it was removed from the i40e,
> + iavf and ice drivers.
> +
>
> Removed Items
> -------------
> --
I think the deprecation notice can be removed, too.
Also, like with the cover letter, it's worth explaining that the SSE paths
are replaced by the AVX2 and AVX-512 paths which offer better performance.
/Bruce
prev parent reply other threads:[~2025-08-25 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 12:35 [PATCH 0/4] Remove SSE from some Intel drivers 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-25 12:35 ` [PATCH 4/4] doc: add release note entry for SSE removal Ciara Loftus
2025-08-25 13:20 ` Bruce Richardson [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=aKxjDpR8d75HtxvW@bricha3-mobl1.ger.corp.intel.com \
--to=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).