From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 1/4] net/idpf: use the new common vector capability function
Date: Thu, 11 Sep 2025 15:35:29 +0100 [thread overview]
Message-ID: <aMLeMQOKemomvoO-@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250911143145.3355960-2-ciara.loftus@intel.com>
On Thu, Sep 11, 2025 at 02:31:42PM +0000, Ciara Loftus wrote:
> Use the new function for determining the maximum simd bitwidth in the
> idpf driver. An additional check is required for the AVX512DQ flag which
> is not performed in the common function. Since no other drivers require
> this flag, the check will remain outside of the common function.
>
DQ can just be checked in the common function too. It was introduced the
same time as AVX-512VL and BW (see [1]). There is no need for special-case
handling of it.
/Bruce
[1] https://en.wikipedia.org/wiki/AVX-512#Instruction_set
next prev parent reply other threads:[~2025-09-11 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 14:31 [PATCH 0/4] idpf and cpfl rx path selection simplification Ciara Loftus
2025-09-11 14:31 ` [PATCH 1/4] net/idpf: use the new common vector capability function Ciara Loftus
2025-09-11 14:35 ` Bruce Richardson [this message]
2025-09-11 14:31 ` [PATCH 2/4] net/idpf: use the common Rx path selection infrastructure Ciara Loftus
2025-09-11 16:21 ` Bruce Richardson
2025-09-11 14:31 ` [PATCH 3/4] net/cpfl: use the new common vector capability function Ciara Loftus
2025-09-11 14:31 ` [PATCH 4/4] net/cpfl: use the common Rx path selection infrastructure Ciara Loftus
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=aMLeMQOKemomvoO-@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).