From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: david@redhat.com
Cc: Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
gregkh@linuxfoundation.org, mingo@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
dan.j.williams@intel.com, Michal Hocko <mhocko@suse.com>,
jack@suse.cz, mawilcox@microsoft.com, jglisse@redhat.com,
Souptick Joarder <jrdr.linux@gmail.com>,
kirill.shutemov@linux.intel.com, Vlastimil Babka <vbabka@suse.cz>,
osalvador@techadventures.net, yasu.isimatu@gmail.com,
malat@debian.org, Mel Gorman <mgorman@suse.de>,
iamjoonsoo.kim@lge.com
Subject: Re: [PATCH v1] mm: inititalize struct pages when adding a section
Date: Fri, 27 Jul 2018 13:25:45 -0400 [thread overview]
Message-ID: <CAGM2reYOat1bxBi0KCZAKrh0YS2PX=w-AkpesuuNVY26SSDu9A@mail.gmail.com> (raw)
In-Reply-To: <20180727165454.27292-1-david@redhat.com>
Hi David,
On Fri, Jul 27, 2018 at 12:55 PM David Hildenbrand <david@redhat.com> wrote:
>
> Right now, struct pages are inititalized when memory is onlined, not
> when it is added (since commit d0dc12e86b31 ("mm/memory_hotplug: optimize
> memory hotplug")).
>
> remove_memory() will call arch_remove_memory(). Here, we usually access
> the struct page to get the zone of the pages.
>
> So effectively, we access stale struct pages in case we remove memory that
> was never onlined.
Yeah, this is a bug, thank you for catching it.
> So let's simply inititalize them earlier, when the
> memory is added. We only have to take care of updating the zone once we
> know it. We can use a dummy zone for that purpose.
>
> So effectively, all pages will already be initialized and set to
> reserved after memory was added but before it was onlined (and even the
> memblock is added). We only inititalize pages once, to not degrade
> performance.
Yes, but we still add one more npages loop, so there will be some
performance degradation, but not severe.
There are many conflicts with linux-next, please sync before sending
out next patch.
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -1162,7 +1162,15 @@ static inline void set_page_address(struct page *page, void *address)
> {
> page->virtual = address;
> }
> +static void set_page_virtual(struct page *page, and enum zone_type zone)
> +{
> + /* The shift won't overflow because ZONE_NORMAL is below 4G. */
> + if (!is_highmem_idx(zone))
> + set_page_address(page, __va(pfn << PAGE_SHIFT));
> +}
> #define page_address_init() do { } while(0)
> +#else
> +#define set_page_virtual(page, zone) do { } while(0)
> #endif
Please use inline functions for both if WANT_PAGE_VIRTUAL case and else case.
> #if defined(HASHED_PAGE_VIRTUAL)
> @@ -2116,6 +2124,8 @@ extern unsigned long find_min_pfn_with_active_regions(void);
> extern void free_bootmem_with_active_regions(int nid,
> unsigned long max_low_pfn);
> extern void sparse_memory_present_with_active_regions(int nid);
> +extern void __meminit init_single_page(struct page *page, unsigned long pfn,
> + unsigned long zone, int nid);
I do not like making init_single_page() public. There is less chance
it is going to be inlined. I think a better way is to have a new
variant of memmap_init_zone that will handle hotplug case.
>
> #endif /* CONFIG_HAVE_MEMBLOCK_NODE_MAP */
>
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 7deb49f69e27..3f28ca3c3a33 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -250,6 +250,7 @@ static int __meminit __add_section(int nid, unsigned long phys_start_pfn,
> struct vmem_altmap *altmap, bool want_memblock)
> {
> int ret;
> + int i;
>
> if (pfn_valid(phys_start_pfn))
> return -EEXIST;
> @@ -258,6 +259,23 @@ static int __meminit __add_section(int nid, unsigned long phys_start_pfn,
> if (ret < 0)
> return ret;
>
> + /*
> + * Initialize all pages in the section before fully exposing them to the
> + * system so nobody will stumble over a half inititalized state.
> + */
> + for (i = 0; i < PAGES_PER_SECTION; i++) {
> + unsigned long pfn = phys_start_pfn + i;
> + struct page *page;
> +
> + if (!pfn_valid(pfn))
> + continue;
> + page = pfn_to_page(pfn);
> +
> + /* dummy zone, the actual one will be set when onlining pages */
> + init_single_page(page, pfn, ZONE_NORMAL, nid);
> + SetPageReserved(page);
> + }
Please move all of the above into a new memmap_init_hotplug() that
should be located in page_alloc.c
> @@ -5519,9 +5515,12 @@ void __meminit memmap_init_zone(unsigned long size, int nid, unsigned long zone,
>
> not_early:
> page = pfn_to_page(pfn);
> - __init_single_page(page, pfn, zone, nid);
> - if (context == MEMMAP_HOTPLUG)
> - SetPageReserved(page);
> + if (context == MEMMAP_HOTPLUG) {
> + /* everything but the zone was inititalized */
> + set_page_zone(page, zone);
> + set_page_virtual(page, zone);
> + } else
> + init_single_page(page, pfn, zone, nid);
>
Please add a new function:
memmap_init_zone_hotplug() that will handle only the zone and virtual
fields for onlined hotplug memory.
Please remove: "enum memmap_context context" from everywhere.
Thank you,
Pavel
next prev parent reply other threads:[~2018-07-27 17:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 16:54 David Hildenbrand
2018-07-27 17:25 ` Pavel Tatashin [this message]
2018-07-27 18:01 ` David Hildenbrand
2018-07-30 11:30 ` Michal Hocko
2018-07-30 11:53 ` David Hildenbrand
2018-07-30 12:05 ` Michal Hocko
2018-07-30 12:11 ` David Hildenbrand
2018-07-30 13:30 ` Pavel Tatashin
2018-07-30 13:51 ` David Hildenbrand
2018-07-30 14:10 ` Michal Hocko
2018-07-30 14:42 ` David Hildenbrand
2018-07-30 14:50 ` Michal Hocko
2018-07-30 15:03 ` David Hildenbrand
2018-07-30 15:45 ` Pavel Tatashin
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='CAGM2reYOat1bxBi0KCZAKrh0YS2PX=w-AkpesuuNVY26SSDu9A@mail.gmail.com' \
--to=pasha.tatashin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malat@debian.org \
--cc=mawilcox@microsoft.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=osalvador@techadventures.net \
--cc=vbabka@suse.cz \
--cc=yasu.isimatu@gmail.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