[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOAebxuwVqjbKuHfpNn9=YBR397pjK-QfF-Akh7UuoEfkW0PWw@mail.gmail.com>
Date: Fri, 16 Feb 2018 08:09:15 -0500
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Steve Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Michal Hocko <mhocko@...e.com>,
Linux Memory Management List <linux-mm@...ck.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Vlastimil Babka <vbabka@...e.cz>,
Bharata B Rao <bharata@...ux.vnet.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, dan.j.williams@...el.com,
kirill.shutemov@...ux.intel.com, bhe@...hat.com
Subject: Re: [v4 5/6] mm/memory_hotplug: don't read nid from struct page
during hotplug
> The namespace of all these memory range handling functions is horribly random,
> and I think now it got worse: we add an assumption that register_new_memory() is
> implicitly called as part of hotplugged memory (where things are pre-cleared) -
> but nothing in its naming suggests so.
>
> How about renaming it to hotplug_memory_register() or so?
Sure, I will rename it.
>
> With that change you can add:
>
> Reviewed-by: Ingo Molnar <mingo@...nel.org>
Thank you,
Pavel
Powered by blists - more mailing lists