From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <ruifeng.wang@arm.com>
Subject: [PATCH] config/arm: make SoC-generic more generic
Date: Tue, 15 Nov 2022 02:09:48 +0000 [thread overview]
Message-ID: <20221115020948.18356-1-fengchengwen@huawei.com> (raw)
The non-generic soc has 1280 max-lcores and 32 max-numas, but the
implementer-generic still has 256 max-lcores and 4 max-numas, which may
result in restrictions on the use of binaries compiled by soc-generic
in these systems.
This patch changes the soc-generic max-lcores to 1280 and max-numas to
32 to make it more generic.
Also, because single numa is a special case of multiple numas, mark
soc-generic's numa flag as true.
Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
---
config/arm/meson.build | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/config/arm/meson.build b/config/arm/meson.build
index 6442ec9596..97b91cf609 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -32,8 +32,8 @@ implementer_generic = {
'flags': [
['RTE_MACHINE', '"armv8a"'],
['RTE_USE_C11_MEM_MODEL', true],
- ['RTE_MAX_LCORE', 256],
- ['RTE_MAX_NUMA_NODES', 4]
+ ['RTE_MAX_LCORE', 1280],
+ ['RTE_MAX_NUMA_NODES', 32]
],
'part_number_config': {
'generic': {
@@ -271,7 +271,8 @@ implementers = {
soc_generic = {
'description': 'Generic un-optimized build for armv8 aarch64 exec mode',
'implementer': 'generic',
- 'part_number': 'generic'
+ 'part_number': 'generic',
+ 'numa': true
}
soc_generic_aarch32 = {
--
2.17.1
next reply other threads:[~2022-11-15 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 2:09 Chengwen Feng [this message]
2022-11-15 7:08 ` Jerin Jacob
2022-11-15 7:55 ` fengchengwen
2022-11-15 8:20 ` Ruifeng Wang
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=20221115020948.18356-1-fengchengwen@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=ruifeng.wang@arm.com \
--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).