From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Reza Arbab <arbab@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Bharata B Rao <bharata@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Stewart Smith <stewart@linux.vnet.ibm.com>,
Alistair Popple <apopple@au1.ibm.com>,
Balbir Singh <bsingharora@gmail.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 4/5] powerpc/mm: restore top-down allocation when using movable_node
Date: Tue, 27 Sep 2016 07:12:31 +1000 [thread overview]
Message-ID: <1474924351.2857.255.camel@kernel.crashing.org> (raw)
In-Reply-To: <1474828616-16608-5-git-send-email-arbab@linux.vnet.ibm.com>
On Sun, 2016-09-25 at 13:36 -0500, Reza Arbab wrote:
> At boot, the movable_node option sets bottom-up memblock allocation.
>
> This reduces the chance that, in the window before movable memory has
> been identified, an allocation for the kernel might come from a movable
> node. By going bottom-up, early allocations will most likely come from
> the same node as the kernel image, which is necessarily in a nonmovable
> node.
>
> Then, once any known hotplug memory has been marked, allocation can be
> reset back to top-down. On x86, this is done in numa_init(). This patch
> does the same on power, in numa initmem_init().
That's fragile and a bit gross.
But then I'm not *that* fan of making accelerator memory be "memory" nodes
in the first place. Oh well...
In any case, if the memory hasn't been hotplug, this shouldn't be necessary
as we shouldn't be considering it for allocation.
If we want to prevent it for other reason, we should add logic for that
in memblock, or reserve it early or something like that.
Just relying magically on the direction of the allocator is bad, really bad.
Ben.
> Signed-off-by: Reza Arbab <arbab@linux.vnet.ibm.com>
> ---
> arch/powerpc/mm/numa.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
> index d7ac419..fdf1e69 100644
> --- a/arch/powerpc/mm/numa.c
> +++ b/arch/powerpc/mm/numa.c
> @@ -945,6 +945,9 @@ void __init initmem_init(void)
> > max_low_pfn = memblock_end_of_DRAM() >> PAGE_SHIFT;
> > max_pfn = max_low_pfn;
>
> > + /* bottom-up allocation may have been set by movable_node */
> > + memblock_set_bottom_up(false);
> +
> > if (parse_numa_properties())
> > setup_nonnuma();
> > else
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-09-26 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 18:36 [PATCH v3 0/5] powerpc/mm: movable hotplug memory nodes Reza Arbab
2016-09-25 18:36 ` [PATCH v3 1/5] drivers/of: introduce of_fdt_is_available() Reza Arbab
2016-10-03 15:28 ` Rob Herring
2016-09-25 18:36 ` [PATCH v3 2/5] drivers/of: do not add memory for unavailable nodes Reza Arbab
2016-09-25 18:36 ` [PATCH v3 3/5] powerpc/mm: allow memory hotplug into a memoryless node Reza Arbab
2016-09-25 18:36 ` [PATCH v3 4/5] powerpc/mm: restore top-down allocation when using movable_node Reza Arbab
2016-09-26 15:47 ` Aneesh Kumar K.V
2016-09-26 20:48 ` Reza Arbab
2016-09-26 21:12 ` Benjamin Herrenschmidt [this message]
2016-09-27 0:14 ` Reza Arbab
2016-10-04 0:48 ` Balbir Singh
2016-10-04 20:23 ` Reza Arbab
2016-09-25 18:36 ` [PATCH v3 5/5] mm: enable CONFIG_MOVABLE_NODE on powerpc Reza Arbab
[not found] ` <1474828616-16608-6-git-send-email-arbab-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-09-26 15:48 ` Aneesh Kumar K.V
2016-09-26 21:15 ` Benjamin Herrenschmidt
2016-09-27 0:19 ` Reza Arbab
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=1474924351.2857.255.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=apopple@au1.ibm.com \
--cc=arbab@linux.vnet.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nfont@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=stewart@linux.vnet.ibm.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).