From: Andre Muezerie <andremue@linux.microsoft.com>
To: David Marchand <david.marchand@redhat.com>,
y@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v4 1/1] mbuf: enable to be compiled with MSVC
Date: Fri, 11 Apr 2025 17:46:15 -0700 [thread overview]
Message-ID: <20250412004615.GA23544@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <20250409134210.GA24610@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Wed, Apr 09, 2025 at 06:42:10AM -0700, Andre Muezerie wrote:
> On Wed, Apr 09, 2025 at 01:39:36PM +0200, David Marchand wrote:
> > On Tue, Apr 8, 2025 at 11:24 PM Andre Muezerie
> > <andremue@linux.microsoft.com> wrote:
> > > diff --git a/lib/net/meson.build b/lib/net/meson.build
> > > index 7a6c419f40..c528fcc9a2 100644
> > > --- a/lib/net/meson.build
> > > +++ b/lib/net/meson.build
> > > @@ -43,7 +43,12 @@ use_function_versioning = true
> > >
> > > if dpdk_conf.has('RTE_ARCH_X86_64')
> > > sources += files('net_crc_sse.c')
> > > - cflags += ['-mpclmul', '-maes']
> > > + cflags_options = ['-mpclmul', '-maes']
> > > + foreach option:cflags_options
> > > + if cc.has_argument(option)
> > > + cflags += option
> > > + endif
> > > + endforeach
> >
> > What guarantee do we have that MSVC builds with those instructions?
> >
>
> The granularity msvc offers for extended instruction sets is different.
> I had sent a patch that allows DPDK code to benefit from those settings,
> but it likely needs to be updated after recent changes were merged. I'll
> revisit that in the next few days.
>
> For reference, here is what the original patch series looked like:
> https://patches.dpdk.org/project/dpdk/list/?series=34803
>
I checked the patch mentioned and confirmed that it still applies cleanly and
that the build succeeds with the patch applied. It's ready to be reviewed.
> > > # only build AVX-512 support if we also have PCLMULQDQ support
> > > if cc.has_argument('-mvpclmulqdq')
> > > sources_avx512 += files('net_crc_avx512.c')
> >
> >
> > --
> > David Marchand
next prev parent reply other threads:[~2025-04-12 0:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 21:51 [PATCH] " Andre Muezerie
2025-02-10 22:34 ` Stephen Hemminger
2025-02-11 2:19 ` Andre Muezerie
2025-02-12 14:23 ` Thomas Monjalon
2025-02-12 16:24 ` Thomas Monjalon
2025-02-19 1:39 ` [PATCH v2 0/5] " Andre Muezerie
2025-02-19 1:39 ` [PATCH v2 1/5] doc: update guide on versioning macros Andre Muezerie
2025-02-19 1:39 ` [PATCH v2 2/5] buildtools: update map_to_win.py to use optional map file Andre Muezerie
2025-02-19 1:39 ` [PATCH v2 3/5] eal: update versioning macros Andre Muezerie
2025-03-06 12:59 ` David Marchand
2025-03-06 15:53 ` Andre Muezerie
2025-02-19 1:39 ` [PATCH v2 4/5] net: update use of " Andre Muezerie
2025-02-19 1:39 ` [PATCH v2 5/5] mbuf: enable to be compiled with MSVC Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 0/6] " Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 1/6] doc: update guide on versioning macros Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 2/6] buildtools: update map_to_win.py to use optional map file Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 3/6] eal: update versioning macros Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 4/6] devtools: check ms linker map files Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 5/6] net: update use of versioning macros Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 6/6] mbuf: enable to be compiled with MSVC Andre Muezerie
2025-04-07 13:53 ` David Marchand
2025-04-08 20:53 ` Andre Muezerie
2025-04-08 21:24 ` [PATCH v4 0/1] " Andre Muezerie
2025-04-08 21:24 ` [PATCH v4 1/1] " Andre Muezerie
2025-04-09 11:39 ` David Marchand
2025-04-09 13:42 ` Andre Muezerie
2025-04-12 0:46 ` Andre Muezerie [this message]
2025-04-10 9:45 ` David Marchand
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=20250412004615.GA23544@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=andremue@linux.microsoft.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=y@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
/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).