From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 3/4] net/ice: remove SSE vector path
Date: Tue, 26 Aug 2025 12:31:26 +0500 [thread overview]
Message-ID: <CA++2-x4mGrxvu7vxRgvQLbtGkS3bMBnLt+1NLpqa9P-GQobsAA@mail.gmail.com> (raw)
In-Reply-To: <20250825123548.1177090-4-ciara.loftus@intel.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Hi Ciara Loftus,
We may need some legacy support for the SSE path for earlier systems. Or it
will not be a problem ?
As you specified that modern x86 systems all support AVX2, if not AVX-512.
Still, we might need some type of support for the SSE path.
Best Regards,
Khadem
On Mon, Aug 25, 2025 at 5:36 PM Ciara Loftus <ciara.loftus@intel.com> wrote:
> 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 in the rare cases where the SSE path would have been used in
> the absence of AVX2 or AVX-512, the fallback scalar path will be used
> which has feature parity with SSE.
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
[-- Attachment #2: Type: text/html, Size: 1190 bytes --]
next prev parent reply other threads:[~2025-08-26 7:31 UTC|newest]
Thread overview: 9+ 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-26 7:31 ` Khadem Ullah [this message]
2025-08-26 7:54 ` Bruce Richardson
2025-08-26 9:29 ` 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
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=CA++2-x4mGrxvu7vxRgvQLbtGkS3bMBnLt+1NLpqa9P-GQobsAA@mail.gmail.com \
--to=14pwcse1224@uetpeshawar.edu.pk \
--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).