[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3e0a47c9-d51d-3d73-e876-abc1c5c81080@suse.cz>
Date: Wed, 14 Jun 2017 11:07:31 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Wei Yang <richard.weiyang@...il.com>,
Michal Hocko <mhocko@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
Mel Gorman <mgorman@...e.de>,
Andrea Arcangeli <aarcange@...hat.com>,
Reza Arbab <arbab@...ux.vnet.ibm.com>,
Yasuaki Ishimatsu <yasu.isimatu@...il.com>,
qiuxishi@...wei.com, Kani Toshimitsu <toshi.kani@....com>,
slaoub@...il.com, Joonsoo Kim <js1304@...il.com>,
Andi Kleen <ak@...ux.intel.com>,
David Rientjes <rientjes@...gle.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
Igor Mammedov <imammedo@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm, memory_hotplug: support movable_node for hotplugable
nodes
On 06/14/2017 11:06 AM, Wei Yang wrote:
> On Mon, Jun 12, 2017 at 08:45:02AM +0200, Michal Hocko wrote:
>> On Mon 12-06-17 12:28:32, Wei Yang wrote:
>>> On Thu, Jun 08, 2017 at 02:23:18PM +0200, Michal Hocko wrote:
>>>> From: Michal Hocko <mhocko@...e.com>
>>>>
>>>> movable_node kernel parameter allows to make hotplugable NUMA
>>>> nodes to put all the hotplugable memory into movable zone which
>>>> allows more or less reliable memory hotremove. At least this
>>>> is the case for the NUMA nodes present during the boot (see
>>>> find_zone_movable_pfns_for_nodes).
>>>>
>>>
>>> When movable_node is enabled, we would have overlapped zones, right?
>>
>> It won't based on this patch. See movable_pfn_range
>
> I did grep in source code, but not find movable_pfn_range.
This patch is adding it.
> Could you share some light on that?
>
>>
Powered by blists - more mailing lists