DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 0/3] allow faster instruction sets to be used with MSVC
Date: Thu, 6 Mar 2025 14:57:04 +0100	[thread overview]
Message-ID: <CAJFAV8wrOkCs9OKg2f87p_qU6qFJQYTS5i-7T8zPvEN5N2XXGA@mail.gmail.com> (raw)
In-Reply-To: <1740604866-6184-1-git-send-email-andremue@linux.microsoft.com>

On Wed, Feb 26, 2025 at 10:21 PM Andre Muezerie
<andremue@linux.microsoft.com> wrote:
>
> Meson.build files were refactored to add MSVC support for the AVX2
> instruction set with MSVC: Top level variable cc_avx2_flags was created
> and set according to the compiler used. It is used in lower level
> directories.
>
> Andre Muezerie (3):
>   eal: make compatible with instruction set updates for MSVC
>   eal: only use numbers as align parameters for MSVC
>   config: create top level variable cc_avx2_flags
>
>  config/x86/meson.build             |  6 ++++++
>  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                |  2 +-
>  lib/eal/common/rte_random.c        |  2 ++
>  lib/eal/x86/include/rte_vect.h     | 11 ++++++++++-
>  12 files changed, 28 insertions(+), 11 deletions(-)

Series applied, thanks André.


-- 
David Marchand


      parent reply	other threads:[~2025-03-06 13:57 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 21:01 [PATCH 0/6] " Andre Muezerie
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-25 14:28   ` Bruce Richardson
2025-02-26  2:01     ` Andre Muezerie
2025-02-26  9:44       ` Bruce Richardson
2025-02-24 21:01 ` [PATCH 4/6] drivers/net: make compatible with instruction set updates for MSVC Andre Muezerie
2025-02-25  9:06   ` Bruce Richardson
2025-02-25 16:44     ` Andre Muezerie
2025-02-24 21:01 ` [PATCH 5/6] acl: " Andre Muezerie
2025-02-25  9:03   ` Bruce Richardson
2025-02-25 16:37     ` Andre Muezerie
2025-02-25 17:21       ` Bruce Richardson
2025-02-25 17:23         ` Andre Muezerie
2025-02-24 21:01 ` [PATCH 6/6] member: " Andre Muezerie
2025-02-26  1:06 ` [PATCH v2 0/5] allow faster instruction sets to be used with MSVC Andre Muezerie
2025-02-26  1:06   ` [PATCH v2 1/5] eal: make compatible with instruction set updates for MSVC Andre Muezerie
2025-02-26  9:50     ` Bruce Richardson
2025-02-26  1:06   ` [PATCH v2 2/5] eal: only use numbers as align parameters " Andre Muezerie
2025-02-26  9:51     ` Bruce Richardson
2025-02-26 10:15     ` Konstantin Ananyev
2025-02-26  1:06   ` [PATCH v2 3/5] config: create top level variable cc_avx2_flags Andre Muezerie
2025-02-26  9:52     ` Bruce Richardson
2025-02-26  1:06   ` [PATCH v2 4/5] drivers/net: make compatible with instruction set updates for MSVC Andre Muezerie
2025-02-26  9:53     ` Bruce Richardson
2025-02-26  1:06   ` [PATCH v2 5/5] acl: " Andre Muezerie
2025-02-26  9:54     ` Bruce Richardson
2025-02-26 21:21 ` [PATCH v3 0/3] allow faster instruction sets to be used with MSVC Andre Muezerie
2025-02-26 21:21   ` [PATCH v3 1/3] eal: make compatible with instruction set updates for MSVC Andre Muezerie
2025-02-26 21:21   ` [PATCH v3 2/3] eal: only use numbers as align parameters " Andre Muezerie
2025-02-27  8:39     ` Konstantin Ananyev
2025-02-26 21:21   ` [PATCH v3 3/3] config: create top level variable cc_avx2_flags Andre Muezerie
2025-03-06 13:57   ` David Marchand [this message]

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=CAJFAV8wrOkCs9OKg2f87p_qU6qFJQYTS5i-7T8zPvEN5N2XXGA@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=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).