From: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Andre Muezerie <andremue@linux.microsoft.com>
Subject: [PATCH 0/6] allow faster instruction sets to be used with MSVC
Date: Mon, 24 Feb 2025 13:01:13 -0800 [thread overview]
Message-ID: <1740430879-17874-1-git-send-email-andremue@linux.microsoft.com> (raw)
Up to now MSVC has being used with the default mode, which uses SSE2
instructions for scalar floating-point and vector calculations.
https://learn.microsoft.com/en-us/cpp/build/reference/arch-x64?view=msvc-170
This series allows users to specify the CPU for which the generated
code should be optimized for in the same way it's done for GCC: by
passing the CPU name.
When no explicit CPU name is passed, 'native' is assumed (like it
happens with GCC) and the code will be optimized for the same CPU
type used to compile the code.
MSVC does not provide this functionality natively, so logic was
added to handle these differences, detecting which
instruction sets are supported by the CPU(s), passing the best
options to MSVC and setting the correct macros (like __AVX512F__)
so that the DPDK code can rely on them like it is done with GCC.
Andre Muezerie (6):
eal: make compatible with instruction set updates for MSVC
eal: only use numbers as align parameters for MSVC
config: allow faster instruction sets to be used with MSVC
drivers/net: make compatible with instruction set updates for MSVC
acl: make compatible with instruction set updates for MSVC
member: make compatible with instruction set updates for MSVC
config/x86/meson.build | 364 +++++++++++++++++++++++++----
drivers/net/bnxt/meson.build | 2 +-
drivers/net/enic/meson.build | 2 +-
drivers/net/intel/i40e/meson.build | 2 +-
drivers/net/intel/iavf/meson.build | 2 +-
drivers/net/intel/ice/meson.build | 2 +-
drivers/net/intel/idpf/meson.build | 2 +-
drivers/net/nfp/meson.build | 2 +-
drivers/net/octeon_ep/meson.build | 4 +-
lib/acl/meson.build | 16 +-
lib/eal/common/rte_random.c | 2 +
lib/eal/x86/include/rte_vect.h | 11 +-
lib/member/meson.build | 11 +-
13 files changed, 363 insertions(+), 59 deletions(-)
--
2.48.1.vfs.0.0
next reply other threads:[~2025-02-24 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 21:01 Andre Muezerie [this message]
2025-02-24 21:01 ` [PATCH 1/6] eal: make compatible with instruction set updates for MSVC Andre Muezerie
2025-02-24 21:01 ` [PATCH 2/6] eal: only use numbers as align parameters " Andre Muezerie
2025-02-24 21:01 ` [PATCH 3/6] config: allow faster instruction sets to be used with MSVC Andre Muezerie
2025-02-24 21:01 ` [PATCH 4/6] drivers/net: make compatible with instruction set updates for MSVC Andre Muezerie
2025-02-24 21:01 ` [PATCH 5/6] acl: " Andre Muezerie
2025-02-24 21:01 ` [PATCH 6/6] member: " Andre Muezerie
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=1740430879-17874-1-git-send-email-andremue@linux.microsoft.com \
--to=andremue@linux.microsoft.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).