DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
To: David Marchand <david.marchand@redhat.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Jie Hai <haijie1@huawei.com>,
	nd <nd@arm.com>
Subject: RE: [RFC PATCH] drivers: add generic build of SVE files
Date: Tue, 8 Apr 2025 17:10:36 +0000	[thread overview]
Message-ID: <PAWPR08MB89091370435B1BF51D90E08F9FB52@PAWPR08MB8909.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zKFof8+_mDc7_Nmf=QkTdVDgBVYY2rc+DVZKXDoR8s8A@mail.gmail.com>



> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday, April 7, 2025 10:50 AM
> To: Bruce Richardson <bruce.richardson@intel.com>
> Cc: dev@dpdk.org; Jie Hai <haijie1@huawei.com>
> Subject: Re: [RFC PATCH] drivers: add generic build of SVE files
> 
> On Mon, Apr 7, 2025 at 5:29 PM Bruce Richardson
> <bruce.richardson@intel.com> 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>
> 
> Thanks for working on this additional cleanup.
> 
> 
> > ---
> >  drivers/meson.build          | 27 +++++++++++++++++++++++++++
> >  drivers/net/hns3/meson.build | 22 +---------------------
> >  2 files changed, 28 insertions(+), 21 deletions(-)
> >
> > diff --git a/drivers/meson.build b/drivers/meson.build index
> > b2d2537dc8..a6f0670a2f 100644
> > --- a/drivers/meson.build
> > +++ b/drivers/meson.build
> > @@ -128,6 +128,7 @@ foreach subpath:subdirs
> >          sources = []
> >          sources_avx2 = []
> >          sources_avx512 = []
> > +        sources_sve = []
> >          headers = []
> >          driver_sdk_headers = [] # public headers included by drivers
> >          objs = []
> > @@ -285,6 +286,32 @@ foreach subpath:subdirs
> >              endif
> >          endif
> >
> > +        if (arch_subdir == 'arm' and sources_sve.length() > 0
> > +                and cc.has_argument('-march=armv8.2-a+sve')
> > +                and cc.check_header('arm_sve.h'))
> > +
> > +            if dpdk_conf.has('RTE_HAS_SVE_ACLE')
> > +                sources += sources_sve
> 
> Do we need this special case?
> 
config/meson.build sets 'RTE_CPUFLAG_SVE for all SoCs with SVE support.
For such SoCs RTE_HAS_SVE_ACLE is set to true if SVE ACLE is available.
However,  for some reason soc_cn10k sets RTE_HAS_SVE_ACLE to false even
though SVE is available on that cnxk SoC.

--wathsala

      parent reply	other threads:[~2025-04-08 17:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 15:28 Bruce Richardson
2025-04-07 15:35 ` Bruce Richardson
2025-04-07 15:49 ` David Marchand
2025-04-07 16:10   ` Bruce Richardson
2025-04-08 17:10   ` Wathsala Wathawana Vithanage [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=PAWPR08MB89091370435B1BF51D90E08F9FB52@PAWPR08MB8909.eurprd08.prod.outlook.com \
    --to=wathsala.vithanage@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=haijie1@huawei.com \
    --cc=nd@arm.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).