From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 1/3] net/iavf: fix Tx vector path selection logic again
Date: Thu, 4 Sep 2025 17:59:45 +0100 [thread overview]
Message-ID: <aLnFgWYb77VpIiGd@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250904104440.2167205-2-ciara.loftus@intel.com>
On Thu, Sep 04, 2025 at 10:44:38AM +0000, Ciara Loftus wrote:
> Commit b39aeea703b8 ("net/iavf: fix Tx vector path selection logic")
> fixed an issue which caused the scalar path to be chosen even when the
> AVX-512 path could have been a viable candidate. The commit
> be1a887b83cd ("net/iavf: use the new common vector capability function")
> accidentally undid this fix, so this commit fixes this again, this time
> in a new way due to the changed code landscape since the last fix.
>
> Fixes: be1a887b83cd ("net/iavf: use the new common vector capability function")
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Will squash into existing commit on next-net-intel.
next prev parent reply other threads:[~2025-09-04 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 10:44 [PATCH 0/3] Fixes for iavf Tx path selection Ciara Loftus
2025-09-04 10:44 ` [PATCH 1/3] net/iavf: fix Tx vector path selection logic again Ciara Loftus
2025-09-04 16:59 ` Bruce Richardson [this message]
2025-09-04 10:44 ` [PATCH 2/3] net/iavf: fix a log during Tx path selection Ciara Loftus
2025-09-04 17:00 ` Bruce Richardson
2025-09-04 10:44 ` [PATCH 3/3] net/iavf: fix Tx path selection for VLAN offload Ciara Loftus
2025-09-04 17:10 ` Bruce Richardson
2025-09-04 17:18 ` [PATCH 0/3] Fixes for iavf Tx path selection 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=aLnFgWYb77VpIiGd@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).