From: Andrew Morton <akpm@linux-foundation.org>
To: Linxu Fang <fanglinxu@huawei.com>
Cc: <mhocko@suse.com>, <vbabka@suse.cz>,
<pavel.tatashin@microsoft.com>, <osalvador@suse.de>,
<linux-mm@kvack.org>
Subject: Re: [PATCH V2] mm: fix node spanned pages when we have a node with only zone_movable
Date: Thu, 4 Apr 2019 12:14:27 -0700 [thread overview]
Message-ID: <20190404121427.0959934dbce398b242b6e67e@linux-foundation.org> (raw)
In-Reply-To: <1554370704-18268-1-git-send-email-fanglinxu@huawei.com>
On Thu, 4 Apr 2019 17:38:24 +0800 Linxu Fang <fanglinxu@huawei.com> wrote:
> commit <342332e6a925> ("mm/page_alloc.c: introduce kernelcore=mirror
> option") and series patches rewrote the calculation of node spanned
> pages.
> commit <e506b99696a2> (mem-hotplug: fix node spanned pages when we have a
> movable node), but the current code still has problems,
> when we have a node with only zone_movable and the node id is not zero,
> the size of node spanned pages is double added.
> That's because we have an empty normal zone, and zone_start_pfn or
> zone_end_pfn is not between arch_zone_lowest_possible_pfn and
> arch_zone_highest_possible_pfn, so we need to use clamp to constrain the
> range just like the commit <96e907d13602> (bootmem: Reimplement
> __absent_pages_in_range() using for_each_mem_pfn_range()).
>
> e.g.
> Zone ranges:
> DMA [mem 0x0000000000001000-0x0000000000ffffff]
> DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
> Normal [mem 0x0000000100000000-0x000000023fffffff]
> Movable zone start for each node
> Node 0: 0x0000000100000000
> Node 1: 0x0000000140000000
> Early memory node ranges
> node 0: [mem 0x0000000000001000-0x000000000009efff]
> node 0: [mem 0x0000000000100000-0x00000000bffdffff]
> node 0: [mem 0x0000000100000000-0x000000013fffffff]
> node 1: [mem 0x0000000140000000-0x000000023fffffff]
>
> node 0 DMA spanned:0xfff present:0xf9e absent:0x61
> node 0 DMA32 spanned:0xff000 present:0xbefe0 absent:0x40020
> node 0 Normal spanned:0 present:0 absent:0
> node 0 Movable spanned:0x40000 present:0x40000 absent:0
> On node 0 totalpages(node_present_pages): 1048446
> node_spanned_pages:1310719
> node 1 DMA spanned:0 present:0 absent:0
> node 1 DMA32 spanned:0 present:0 absent:0
> node 1 Normal spanned:0x100000 present:0x100000 absent:0
> node 1 Movable spanned:0x100000 present:0x100000 absent:0
> On node 1 totalpages(node_present_pages): 2097152
> node_spanned_pages:2097152
> Memory: 6967796K/12582392K available (16388K kernel code, 3686K rwdata,
> 4468K rodata, 2160K init, 10444K bss, 5614596K reserved, 0K
> cma-reserved)
>
> It shows that the current memory of node 1 is double added.
> After this patch, the problem is fixed.
>
> node 0 DMA spanned:0xfff present:0xf9e absent:0x61
> node 0 DMA32 spanned:0xff000 present:0xbefe0 absent:0x40020
> node 0 Normal spanned:0 present:0 absent:0
> node 0 Movable spanned:0x40000 present:0x40000 absent:0
> On node 0 totalpages(node_present_pages): 1048446
> node_spanned_pages:1310719
> node 1 DMA spanned:0 present:0 absent:0
> node 1 DMA32 spanned:0 present:0 absent:0
> node 1 Normal spanned:0 present:0 absent:0
> node 1 Movable spanned:0x100000 present:0x100000 absent:0
> On node 1 totalpages(node_present_pages): 1048576
> node_spanned_pages:1048576
> memory: 6967796K/8388088K available (16388K kernel code, 3686K rwdata,
> 4468K rodata, 2160K init, 10444K bss, 1420292K reserved, 0K
> cma-reserved)
>
How does this differ from the previous version you sent?
next prev parent reply other threads:[~2019-04-04 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 9:38 [PATCH V2] mm: fix node spanned pages when we have a node with only zone_movable Linxu Fang
2019-04-04 19:14 ` Andrew Morton [this message]
2019-04-08 4:26 ` Linxu Fang
2019-04-05 12:54 ` Oscar Salvador
2019-04-08 4:18 ` Linxu Fang
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=20190404121427.0959934dbce398b242b6e67e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fanglinxu@huawei.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pavel.tatashin@microsoft.com \
--cc=vbabka@suse.cz \
/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).