DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Cc: <david.marchand@redhat.com>, Jie Hai <haijie1@huawei.com>
Subject: Re: [RFC PATCH] drivers: add generic build of SVE files
Date: Mon, 7 Apr 2025 16:35:01 +0100	[thread overview]
Message-ID: <Z_PwpRYVsXLR1QBk@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250407152857.2203839-1-bruce.richardson@intel.com>

On Mon, Apr 07, 2025 at 04:28:57PM +0100, Bruce Richardson wrote:
> For SVE, as for AVX2 and AVX-512, support building files for these ISAs
> from the top-level drivers/meson.build file, rather than having each
> driver re-implement it.
> 
> This removes the remaining build task for drivers in DPDK which is
> being done by a driver itself, rather than in the generic drivers'
> build rules.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>  drivers/meson.build          | 27 +++++++++++++++++++++++++++
>  drivers/net/hns3/meson.build | 22 +---------------------
>  2 files changed, 28 insertions(+), 21 deletions(-)
> 
As noted in my email in the other thread [1], this code has not been
tested, and is being sent out here as a start point to hopefully enable
someone more familiar with SVE to improve on it as-necessary. This support
of SVE in hns3 driver is the last remaining instance of a driver doing a
separate build of source code itself. All other drivers now simply pass all
code files back to the top level meson.build file to have them built
appropriately there.

/Bruce

[1] https://inbox.dpdk.org/dev/Z_Pvxr5ozfjXI692@bricha3-mobl1.ger.corp.intel.com/T/#m6614ca2fdef698e0448311f7255bf3be2438f101

  reply	other threads:[~2025-04-07 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 15:28 Bruce Richardson
2025-04-07 15:35 ` Bruce Richardson [this message]
2025-04-07 15:49 ` David Marchand
2025-04-07 16:10   ` 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=Z_PwpRYVsXLR1QBk@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=haijie1@huawei.com \
    /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).