DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Cc: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH 3/4] net/ice: remove SSE vector path
Date: Tue, 26 Aug 2025 11:50:18 +0100	[thread overview]
Message-ID: <aK2Rajd8rypPr7lT@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CA++2-x5j0hH3XweLL+=O7-GJOnGSuN8zoFURs13mgFiVh1MD3Q@mail.gmail.com>

On Tue, Aug 26, 2025 at 02:29:28PM +0500, Khadem Ullah wrote:
>    Hi Bruce,
>    Thanks for the feedback!

No problem. 
BTW: Please don't top-post in replying - it's best practice to put
the reply below the text you are replying to. Thanks.

>    I have checked at my end, most of our systems (Intel(R) Xeon(R), AMD
>    EPYC)
>    do support sse, avx, and avx2. I was talking about general
>    availability.

AVX2 was first available in systems starting in 2013, (and AMD systems
since 2015), so at this point it's been around a long time. The SSE code
paths in the drivers will only be used by systems which do not have AVX2 on
them - which should be relatively rare, I hope, at this point. There are no
features in the SSE driver that are not available in the AVX2 one, so, I'm
not aware of any reason why one would need to use the SSE code path in a
deployment of DPDK.

>    It means, newer features will not be added to the SSE path and as
>    you mentioned that LTS 24.11 will provide support till the end of 2027.
>    Applications that use ice SSE paths can benefit from it.

Even without this patch, there will be no features added to the SSE code
paths in the drivers. Any new additions would just be to the AVX2 and
AVX-512 code paths. Even for systems without AVX2, if the SSE path is
removed the driver will fall-back to the scalar paths, which have far more
features available in them than the SSE codepaths, which were simplified for
performance reasons.

/Bruce

>    Best Regards,
>    Khadem
>    On Tue, Aug 26, 2025 at 12:54 PM Bruce Richardson
>    <[1]bruce.richardson@intel.com> wrote:
> 
>      Hi Kadem,
>      can you perhaps share what systems you are using that do not have
>      AVX2
>      support? Do you do new deployments with latest DPDK on those
>      systems?
>      However, if it helps, we can defer this patch till after 25.11
>      release, so that we have one more LTS with SSE support still in it.
>      That
>      would mean that we have a supported DPDK release with SSE in it
>      until
>      potentially end of 2028. As it stands, even if this patch goes into
>      the
>      release, 24.11 will be supported till end of 2027.
>      /Bruce
> 
> References
> 
>    1. mailto:bruce.richardson@intel.com

  reply	other threads:[~2025-08-26 10:50 UTC|newest]

Thread overview: 14+ 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
2025-08-26  7:54     ` Bruce Richardson
2025-08-26  9:29       ` Khadem Ullah
2025-08-26 10:50         ` Bruce Richardson [this message]
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

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=aK2Rajd8rypPr7lT@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=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).