From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v1 0/8] centralize AVX-512 feature detection
Date: Mon, 30 Sep 2024 18:50:24 +0100 [thread overview]
Message-ID: <20240930175033.2283861-1-bruce.richardson@intel.com> (raw)
The meson code to detect CPU and compiler support for AVX512 was duplicated
across multiple drivers. Do all detection in just a single place to simplify
the code.
Bruce Richardson (8):
config/x86: add global defines for checking AVX-512
event/dlb2: use global AVX-512 variables
common/idpf: use global AVX-512 variables
net/cpfl: use global AVX-512 variables
net/i40e: use global AVX-512 variables
net/iavf: use global AVX-512 variables
net/ice: use global AVX-512 variables
net/idpf: use global AVX-512 variables
config/x86/meson.build | 12 +++++++++-
drivers/common/idpf/meson.build | 17 ++-----------
drivers/event/dlb2/meson.build | 42 +++++++--------------------------
drivers/net/cpfl/meson.build | 19 ++-------------
drivers/net/i40e/meson.build | 13 ++--------
drivers/net/iavf/meson.build | 13 ++--------
drivers/net/ice/meson.build | 15 ++----------
drivers/net/idpf/meson.build | 19 ++-------------
8 files changed, 32 insertions(+), 118 deletions(-)
--
2.43.0
next reply other threads:[~2024-09-30 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 17:50 Bruce Richardson [this message]
2024-09-30 17:50 ` [PATCH v1 1/8] config/x86: add global defines for checking AVX-512 Bruce Richardson
2024-09-30 17:50 ` [PATCH v1 2/8] event/dlb2: use global AVX-512 variables Bruce Richardson
2024-09-30 17:50 ` [PATCH v1 3/8] common/idpf: " Bruce Richardson
2024-09-30 17:50 ` [PATCH v1 4/8] net/cpfl: " Bruce Richardson
2024-09-30 17:50 ` [PATCH v1 5/8] net/i40e: " Bruce Richardson
2024-09-30 17:50 ` [PATCH v1 6/8] net/iavf: " Bruce Richardson
2024-09-30 17:50 ` [PATCH v1 7/8] net/ice: " Bruce Richardson
2024-09-30 17:50 ` [PATCH v1 8/8] net/idpf: " 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=20240930175033.2283861-1-bruce.richardson@intel.com \
--to=bruce.richardson@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).