From: Catalin Marinas <catalin.marinas@arm.com>
To: Janghyuck Kim <janghyuck.kim@samsung.com>
Cc: hyesoo.yu@samsung.com, pullip.cho@samsung.com,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: arm64: Kconfig: support for nodes spanning other nodes
Date: Thu, 26 Nov 2020 15:31:44 +0000 [thread overview]
Message-ID: <20201126153144.GB6722@gaia> (raw)
In-Reply-To: <20201029061950.4217-1-janghyuck.kim@samsung.com>
On Thu, Oct 29, 2020 at 03:19:50PM +0900, Janghyuck Kim wrote:
> 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
I guess this patch no longer makes sense after commit acd3f5c441e9 ("mm:
remove early_pfn_in_nid() and CONFIG_NODES_SPAN_OTHER_NODES").
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-26 15:33 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 ` arm64: Kconfig: support for nodes spanning other nodes Janghyuck Kim
2020-11-26 15:31 ` Catalin Marinas [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=20201126153144.GB6722@gaia \
--to=catalin.marinas@arm.com \
--cc=hyesoo.yu@samsung.com \
--cc=janghyuck.kim@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