From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"feifei.wang2@arm.com" <feifei.wang2@arm.com>,
"nd@arm.com" <nd@arm.com>
Subject: RE: [EXT] [PATCH 1/2] config/arm: update config for Neoverse N2
Date: Wed, 7 Jun 2023 15:11:59 +0000 [thread overview]
Message-ID: <PH0PR18MB4086D4BC795D5056FB88EBE6DE53A@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230529055751.3035712-1-ruifeng.wang@arm.com>
> Updated maximum number of lcores and numa nodes to support platforms
> with multiple numa nodes.
> Added mcpu compiler option.
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Feifei Wang <feifei.wang2@arm.com>
> ---
> config/arm/meson.build | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/config/arm/meson.build b/config/arm/meson.build
> index 5213434ca4..9e55e9f2a4 100644
> --- a/config/arm/meson.build
> +++ b/config/arm/meson.build
> @@ -91,11 +91,12 @@ part_number_config_arm = {
> '0xd49': {
> 'march': 'armv8.5-a',
> 'march_features': ['sve2'],
> + 'compiler_options': ['-mcpu=neoverse-n2'],
Hi Ruifeng,
I see the following warning when compiling with GCC 12
cc1: warning: switch '-mcpu=neoverse-n2' conflicts with '-march=armv8.5-a+sve2+crypto' switch
Removing 'armv8.5-a' from the list makes the warning go away but what's the correct march for neoverse-n2?
Armv9.0-a is not a supported march flag in GCC.
> 'flags': [
> ['RTE_MACHINE', '"neoverse-n2"'],
> ['RTE_ARM_FEATURE_ATOMICS', true],
> - ['RTE_MAX_LCORE', 64],
> - ['RTE_MAX_NUMA_NODES', 1]
> + ['RTE_MAX_LCORE', 128],
> + ['RTE_MAX_NUMA_NODES', 2]
> ]
> }
> }
> --
> 2.25.1
next prev parent reply other threads:[~2023-06-07 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 5:57 Ruifeng Wang
2023-05-29 5:57 ` [PATCH 2/2] build: fix warning when running external command Ruifeng Wang
2023-05-29 8:12 ` Bruce Richardson
2023-05-29 7:41 ` [PATCH 1/2] config/arm: update config for Neoverse N2 Juraj Linkeš
2023-06-06 13:51 ` Thomas Monjalon
2023-06-07 15:11 ` Pavan Nikhilesh Bhagavatula [this message]
2023-06-08 4:29 ` [EXT] " Ruifeng Wang
2023-06-08 4:34 ` Pavan Nikhilesh Bhagavatula
2023-06-08 5:25 ` 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=PH0PR18MB4086D4BC795D5056FB88EBE6DE53A@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=feifei.wang2@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@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).