Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752516AbdFAPsD (ORCPT ); Thu, 1 Jun 2017 11:48:03 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:41160 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752498AbdFAPsA (ORCPT ); Thu, 1 Jun 2017 11:48:00 -0400 Date: Thu, 1 Jun 2017 10:47:46 -0500 From: Reza Arbab To: Michal Hocko Cc: Vlastimil Babka , linux-mm@kvack.org, Andrew Morton , Mel Gorman , Andrea Arcangeli , Jerome Glisse , Yasuaki Ishimatsu , qiuxishi@huawei.com, Kani Toshimitsu , slaoub@gmail.com, Joonsoo Kim , Andi Kleen , David Rientjes , Daniel Kiper , Igor Mammedov , Vitaly Kuznetsov , LKML Subject: Re: [RFC PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes References: <20170601122004.32732-1-mhocko@kernel.org> <820164f3-8bef-7761-0695-88db9e0ce7a7@suse.cz> <20170601142227.GF9091@dhcp22.suse.cz> <20170601151935.m5jbfmugocc66qfq@arbab-laptop.localdomain> <20170601153838.GA8088@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20170601153838.GA8088@dhcp22.suse.cz> Organization: IBM Linux Technology Center User-Agent: NeoMutt/20170428 (1.8.2) X-TM-AS-GCONF: 00 x-cbid: 17060115-0044-0000-0000-00000341A22C X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00007153; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000212; SDB=6.00868732; UDB=6.00431758; IPR=6.00648606; BA=6.00005393; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015670; XFM=3.00000015; UTC=2017-06-01 15:47:53 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17060115-0045-0000-0000-0000076FA265 Message-Id: <20170601154746.wjc56eldgyzr2bpm@arbab-laptop.localdomain> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-06-01_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706010293 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 929 Lines: 24 On Thu, Jun 01, 2017 at 05:38:38PM +0200, Michal Hocko wrote: >On Thu 01-06-17 10:19:36, Reza Arbab wrote: >> The x86 SRAT (or the dt, on other platforms) can describe memory as >> hotpluggable. See memblock_mark_hotplug(). That's only for memory present at >> boot, though. > >Yes but lose that information after the memblock is gone and numa fully >initialized. Or can we reconstruct that somehow? I'm not sure you'd have to. At boot time, those markings are used to determine the initial boundaries of ZONE_MOVABLE. So if you removed these memblocks, then readded them, they would still be in ZONE_MOVABLE. >> He's saying that since the memory was added after boot, it is by >> definition hotpluggable. There's no need to check for that >> marking/description. > >Yes, but we do not know whether we are onlining memblocks from a boot >time numa node or a fresh one which has been hotadded. That's true. -- Reza Arbab