From: Will Deacon <will@kernel.org>
To: Hoan Tran OS <hoan@os.amperecomputing.com>
Cc: Open Source Review <OpenSourceReview@amperecomputing.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: Kconfig: Enable NODES_SPAN_OTHER_NODES config for NUMA
Date: Tue, 25 Jun 2019 11:12:45 +0100 [thread overview]
Message-ID: <20190625101245.s4vxfosoop52gl4e@willie-the-truck> (raw)
In-Reply-To: <1561387098-23692-1-git-send-email-Hoan@os.amperecomputing.com>
On Mon, Jun 24, 2019 at 02:38:28PM +0000, Hoan Tran OS wrote:
> 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.
>
> This patch enables NODES_SPAN_OTHER_NODES config for NUMA to support
> this type of NUMA layout.
>
> Signed-off-by: Hoan Tran <Hoan@os.amperecomputing.com>
> ---
> arch/arm64/Kconfig | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 697ea05..21fc168 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -873,6 +873,13 @@ 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.
> +config NODES_SPAN_OTHER_NODES
> + def_bool y
> + depends on ACPI_NUMA
How come this is specific to ACPI?
It would be nice if this was the default, given that only ia64, mips and
sh appear to be the only NUMA-capable architectures which don't have it.
In other words, replace the #ifdef CONFIG_NODES_SPAN_OTHER_NODES in
mm/page_alloc.c with #ifdef CONFIG_NUMA.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-25 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 14:38 [PATCH] arm64: Kconfig: Enable NODES_SPAN_OTHER_NODES config for NUMA Hoan Tran OS
2019-06-25 10:12 ` Will Deacon [this message]
2019-06-25 14:55 ` Hoan Tran OS
2020-02-03 19:55 Hoan Tran
2020-02-06 10:23 ` Will Deacon
2020-02-06 20:01 ` Hoan Tran
2020-02-25 23:20 ` Hoan Tran
2020-03-11 6:31 ` Hoan Tran
2020-03-11 11:27 ` Catalin Marinas
2020-03-28 18:36 ` Hoan Tran
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=20190625101245.s4vxfosoop52gl4e@willie-the-truck \
--to=will@kernel.org \
--cc=OpenSourceReview@amperecomputing.com \
--cc=catalin.marinas@arm.com \
--cc=hoan@os.amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@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).