From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
bruce.richardson@intel.com, Honnappa.Nagarahalli@arm.com,
Ruifeng.Wang@arm.com, ferruh.yigit@intel.com,
christian.ehrhardt@canonical.com, stephen@networkplumber.org
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [PATCH v2] config/arm: add armv7 native config
Date: Tue, 25 Jan 2022 11:08:28 +0100 [thread overview]
Message-ID: <1643105308-26026-1-git-send-email-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <1637232351-21856-1-git-send-email-juraj.linkes@pantheon.tech>
Armv7 native build fails with this error:
../config/meson.build:364:1: ERROR: Problem encountered:
Number of CPU cores not specified.
This is because RTE_MAX_LCORE is not set. We also need to set
RTE_MAX_NUMA_NODES in armv7 native builds.
Fixes: 8ef09fdc506b ("build: add optional NUMA and CPU counts detection")
Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
---
config/arm/meson.build | 2 ++
1 file changed, 2 insertions(+)
diff --git a/config/arm/meson.build b/config/arm/meson.build
index c3a3f2faaf..a0e91c0f6b 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -434,6 +434,8 @@ if dpdk_conf.get('RTE_ARCH_32')
# armv7 build
dpdk_conf.set('RTE_ARCH_ARMv7', true)
dpdk_conf.set('RTE_ARCH', 'armv7')
+ dpdk_conf.set('RTE_MAX_LCORE', 128)
+ dpdk_conf.set('RTE_MAX_NUMA_NODES', 1)
# the minimum architecture supported, armv7-a, needs the following,
machine_args += '-mfpu=neon'
endif
--
2.20.1
next prev parent reply other threads:[~2022-01-25 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 10:45 [PATCH v1] " Juraj Linkeš
2021-12-31 7:11 ` Ruifeng Wang
2021-12-31 17:23 ` Stephen Hemminger
2022-01-25 10:08 ` Juraj Linkeš [this message]
2022-02-10 16:34 ` [PATCH v2] " Thomas Monjalon
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=1643105308-26026-1-git-send-email-juraj.linkes@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.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).