Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751990AbdFNJJP (ORCPT ); Wed, 14 Jun 2017 05:09:15 -0400 Received: from mx2.suse.de ([195.135.220.15]:45662 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751989AbdFNJIM (ORCPT ); Wed, 14 Jun 2017 05:08:12 -0400 Subject: Re: [PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes To: Wei Yang , Michal Hocko Cc: Andrew Morton , linux-mm@kvack.org, Mel Gorman , Andrea Arcangeli , Reza Arbab , Yasuaki Ishimatsu , qiuxishi@huawei.com, Kani Toshimitsu , slaoub@gmail.com, Joonsoo Kim , Andi Kleen , David Rientjes , Daniel Kiper , Igor Mammedov , Vitaly Kuznetsov , LKML References: <20170608122318.31598-1-mhocko@kernel.org> <20170612042832.GA7429@WeideMBP.lan> <20170612064502.GD4145@dhcp22.suse.cz> <20170614090651.GA15288@WeideMacBook-Pro.local> From: Vlastimil Babka Message-ID: <3e0a47c9-d51d-3d73-e876-abc1c5c81080@suse.cz> Date: Wed, 14 Jun 2017 11:07:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170614090651.GA15288@WeideMacBook-Pro.local> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 845 Lines: 24 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 >>>> >>>> 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? > >>