DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 0/4] Remove SSE from some Intel drivers
Date: Thu, 11 Dec 2025 12:25:30 +0000	[thread overview]
Message-ID: <aTq4OhjqR1z9Okew@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250825123548.1177090-1-ciara.loftus@intel.com>

On Mon, Aug 25, 2025 at 12:35:44PM +0000, Ciara Loftus wrote:
> This patch removes the SSE Rx and Tx paths from the i40e, iavf and ice
> driverss. Each of these drivers have faster vector paths (AVX2 and AVX-512)
> which have feature parity with the SSE paths. In environments where AVX2 or
> AVX-512 are not supported, the scalar path will still be used, which also
> has feature parity.
> 
> This series is intended for the next-net-intel tree.
> 
I'm going to hopefully take the Tx path selection logic patchset first, so
this set should be rebased on top of the v2 of that set.

Thanks,
/Bruce

      parent reply	other threads:[~2025-12-11 12:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 12:35 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 ` 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=aTq4OhjqR1z9Okew@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).