From: Joyce Kong <joyce.kong@arm.com>
To: gavin.hu@arm.com
Cc: joyce.kong@arm.com, stable@dpdk.org
Subject: [dpdk-stable] [PATCH 2/2] config: enable more than 128 cores for meson build
Date: Wed, 21 Nov 2018 18:52:21 +0800 [thread overview]
Message-ID: <1542797541-46330-2-git-send-email-joyce.kong@arm.com> (raw)
In-Reply-To: <1542797541-46330-1-git-send-email-joyce.kong@arm.com>
When running dpdk applications on cores whose ids are bigger
than original max_core setting, eal error as below:
EAL: Detected 104 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: invalid core list
-l CORELIST core indexes between 0 and 128
The fix is to increase max_core to 256 on thundex platform
for meson build.
Fixes: 200b88cb ("build: detect micro-arch on ARM")
Cc: stable@dpdk.org
Signed-off-by: Joyce Kong <joyce.kong@arm.com>
Reviewed-by: Gavin Hu <gavin.hu@arm.com>
---
config/arm/meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config/arm/meson.build b/config/arm/meson.build
index b755138..020df09 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -51,7 +51,7 @@ flags_cavium = [
['RTE_MACHINE', '"thunderx"'],
['RTE_CACHE_LINE_SIZE', 128],
['RTE_MAX_NUMA_NODES', 2],
- ['RTE_MAX_LCORE', 96],
+ ['RTE_MAX_LCORE', 256],
['RTE_MAX_VFIO_GROUPS', 128],
['RTE_USE_C11_MEM_MODEL', false]]
flags_dpaa = [
--
2.7.4
next prev parent reply other threads:[~2018-11-21 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 10:52 [dpdk-stable] [PATCH 1/2] config: enable more than 128 cores for Arm platform Joyce Kong
2018-11-21 10:52 ` Joyce Kong [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-21 10:50 Joyce Kong
2018-11-21 10:50 ` [dpdk-stable] [PATCH 2/2] config: enable more than 128 cores for meson build Joyce Kong
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=1542797541-46330-2-git-send-email-joyce.kong@arm.com \
--to=joyce.kong@arm.com \
--cc=gavin.hu@arm.com \
--cc=stable@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).