From: Janghyuck Kim <janghyuck.kim@samsung.com>
To: unlisted-recipients:; (no To-header on input)
Cc: janghyuck.kim@samsung.com, hyesoo.yu@samsung.com,
pullip.cho@samsung.com, Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: arm64: Kconfig: support for nodes spanning other nodes
Date: Thu, 29 Oct 2020 15:19:50 +0900 [thread overview]
Message-ID: <20201029061950.4217-1-janghyuck.kim@samsung.com> (raw)
In-Reply-To: CGME20201029060015epcas2p2c9969a6782d8214bcbefa36ffad8e10c@epcas2p2.samsung.com
To support NUMA systems whose physical address layout is not continuous
on one node, nodes spanning other nodes feature is required.
Signed-off-by: Janghyuck Kim <janghyuck.kim@samsung.com>
---
arch/arm64/Kconfig | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 49b8d017cba6..18ff7ce9dd60 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -1004,6 +1004,14 @@ config NEED_PER_CPU_EMBED_FIRST_CHUNK
config HOLES_IN_ZONE
def_bool y
+# Some NUMA nodes have memory ranges that span
+# other nodes. Even though a pfn is valid and
+# between a node's start and end pfns, it may not
+# reside on that node. See memmap_init_zone()
+# for details.
+config NODES_SPAN_OTHER_NODES
+ depends on NUMA
+
source "kernel/Kconfig.hz"
config ARCH_SUPPORTS_DEBUG_PAGEALLOC
--
2.28.0
next parent reply other threads:[~2020-10-29 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201029060015epcas2p2c9969a6782d8214bcbefa36ffad8e10c@epcas2p2.samsung.com>
2020-10-29 6:19 ` Janghyuck Kim [this message]
2020-11-26 15:31 ` arm64: Kconfig: support for nodes spanning other nodes Catalin Marinas
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=20201029061950.4217-1-janghyuck.kim@samsung.com \
--to=janghyuck.kim@samsung.com \
--cc=catalin.marinas@arm.com \
--cc=hyesoo.yu@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pullip.cho@samsung.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).