From: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
To: linux-arm-kernel@lists.infradead.org
Cc: patches@amperecomputing.com, linux-kernel@vger.kernel.org,
Anshuman.Khandual@arm.com, Valentin.Schneider@arm.com,
catalin.marinas@arm.com, will@kernel.org,
Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
Subject: [PATCH v3] arm64: NUMA: Kconfig: Increase NODES_SHIFT to 4
Date: Fri, 30 Oct 2020 10:30:50 -0700 [thread overview]
Message-ID: <20201030173050.1182876-1-vanshikonda@os.amperecomputing.com> (raw)
The current arm64 default config limits max NUMA nodes available on
system to 4 (NODES_SHIFT = 2). Today's arm64 systems can reach or
exceed 16 NUMA nodes. To accomodate current hardware and to fit
NODES_SHIFT within page flags on arm64, increase NODES_SHIFT to 4.
Discussion on v1 of the patch:
https://lore.kernel.org/linux-arm-kernel/20201020173409.1266576-1-vanshikonda@os.amperecomputing.com/
-v2: Updated commit message based on discussion
-v3: Updated link to v1 discussion
Signed-off-by: Vanshidhar Konda <vanshikonda@os.amperecomputing.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
---
arch/arm64/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index f858c352f72a..cffcc677011f 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -982,7 +982,7 @@ config NUMA
config NODES_SHIFT
int "Maximum NUMA Nodes (as a power of 2)"
range 1 10
- default "2"
+ default "4"
depends on NEED_MULTIPLE_NODES
help
Specify the maximum number of NUMA Nodes available on the target
--
2.28.0
next reply other threads:[~2020-10-30 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 17:30 Vanshidhar Konda [this message]
2020-11-03 14:54 ` [PATCH v3] arm64: NUMA: Kconfig: Increase NODES_SHIFT to 4 Will Deacon
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=20201030173050.1182876-1-vanshikonda@os.amperecomputing.com \
--to=vanshikonda@os.amperecomputing.com \
--cc=Anshuman.Khandual@arm.com \
--cc=Valentin.Schneider@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=will@kernel.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).