[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0e67afe465cbbdf6ec9b122f596910cae77bc734.camel@linux.ibm.com>
Date: Thu, 18 Jul 2019 12:50:29 -0300
From: Leonardo Bras <leonardo@...ux.ibm.com>
To: Oscar Salvador <osalvador@...e.de>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Michal Hocko <mhocko@...e.com>,
Pavel Tatashin <pasha.tatashin@...cle.com>,
Jérôme Glisse <jglisse@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Pasha Tatashin <Pavel.Tatashin@...rosoft.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Subject: Re: [PATCH 1/1] mm/memory_hotplug: Adds option to hot-add memory in
ZONE_MOVABLE
On Thu, 2019-07-18 at 08:12 +0200, Oscar Salvador wrote:
> We do already have "movable_node" boot option, which exactly has that
> effect.
> Any hotplugged range will be placed in ZONE_MOVABLE.
Oh, I was not aware of it.
> Why do we need yet another option to achieve the same? Was not that
> enough for your case?
Well, another use of this config could be doing this boot option a
default on any given kernel.
But in the above case I agree it would be wiser to add the code on
movable_node_is_enabled() directly, and not where I did put.
What do you think about it?
Thanks for the feedback,
Leonardo Brás
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists