From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: Jan Viktorin <viktorin@rehivetech.com>, dev <dev@dpdk.org>,
Luca Boccassi <bluca@debian.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>, nd <nd@arm.com>
Subject: RE: Probing the expected state/support of DPDK@armhf
Date: Thu, 18 Nov 2021 10:28:30 +0000 [thread overview]
Message-ID: <299f700b98564494b7937a736ba438a9@pantheon.tech> (raw)
In-Reply-To: <AS8PR08MB7080D40C57E9F2AD111DA66C9E9A9@AS8PR08MB7080.eurprd08.prod.outlook.com>
> > > > > What I see when building DPDK 21.11 is
> > > > > 2973 ../config/meson.build:364:1: ERROR: Problem encountered:
> > > > > Number of CPU cores not specified.
> > > > >
> > > > > Right now this seems to be broken the same everywhere - Suse
> > > > > [1], fedora [2], Debian/Ubuntu [3]
> > > > Looks like this happens with native build on armv7 machine.
> > > > RTE_MAX_LCORE
> > > is not set for the build.
> > >
> >
> > What do we want to do with armv7 native build, Ruifeng? For aarch64,
> > we detect which machine we're building on and we set everything
> > accordingly, unless the generic build is enabled. Do we want to add
> > support for just the generic build for armv7 (i.e. regardless of
> > what's set in -Dplatform)? What values of RTE_MAX_LCORE and
> > RTE_MAX_NUMA_NODES make sense for an
> > armv7 generic build?
>
> Yes, support just the generic build for armv7.
> I think we should have RTE_MAX_LCORE=128, RTE_MAX_NUMA_NODES=8 for
> the build.
> These values are consistent with values used in stable branch where armv7 still
> have Make build support.
Ok, I'll submit a patch.
prev parent reply other threads:[~2021-11-18 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 12:32 [dpdk-dev] " Christian Ehrhardt
2021-11-09 7:17 ` Ruifeng Wang
2021-11-10 7:47 ` Christian Ehrhardt
2021-11-16 12:06 ` Juraj Linkeš
2021-11-17 6:44 ` Ruifeng Wang
2021-11-18 10:28 ` Juraj Linkeš [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=299f700b98564494b7937a736ba438a9@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=viktorin@rehivetech.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).