From: Doug Foster <Doug.Foster@arm.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Olivier Matz <olivier.matz@6wind.com>
Subject: RE: [PATCH] config/arm: fix inconsistency for Neoverse N2
Date: Thu, 23 Oct 2025 00:28:03 +0000 [thread overview]
Message-ID: <AS8PR08MB7339DA678541942C52F92D3AE5F0A@AS8PR08MB7339.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20251016080533.535266-1-thierry.herbelot@6wind.com>
Acked-by: Doug Foster <doug.foster@arm.com>
>-----Original Message-----
>From: Thierry Herbelot <thierry.herbelot@6wind.com>
>Sent: Thursday, October 16, 2025 3:06 AM
>To: dev@dpdk.org
>Cc: Thierry Herbelot <thierry.herbelot@6wind.com>; thomas@monjalon.net;
>Bruce Richardson <bruce.richardson@intel.com>; Wathsala Vithanage
><wathsala.vithanage@arm.com>; stable@dpdk.org; Olivier Matz
><olivier.matz@6wind.com>
>Subject: [PATCH] config/arm: fix inconsistency for Neoverse N2
>
>Configuration for hex code '0xd49' enables two NUMA nodes.
>Then, the corresponding 'soc_n2' should allow 'numa'.
>
>Fixes: ea85ed1f6882 ("config/arm: increase nodes and cores for Neoverse N2")
>Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.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
>665f3fa38fcf..316f23941996 100644
>--- a/config/arm/meson.build
>+++ b/config/arm/meson.build
>@@ -590,7 +590,7 @@ soc_n2 = {
> 'description': 'Arm Neoverse N2',
> 'implementer': '0x41',
> 'part_number': '0xd49',
>- 'numa': false
>+ 'numa': true
> }
>
> soc_n3 = {
>--
>2.39.2
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
prev parent reply other threads:[~2025-10-23 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 8:05 Thierry Herbelot
2025-10-23 0:28 ` Doug Foster [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=AS8PR08MB7339DA678541942C52F92D3AE5F0A@AS8PR08MB7339.eurprd08.prod.outlook.com \
--to=doug.foster@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
--cc=thierry.herbelot@6wind.com \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@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).