From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f69.google.com (mail-wm0-f69.google.com [74.125.82.69]) by kanga.kvack.org (Postfix) with ESMTP id 016A86B0292 for ; Mon, 29 May 2017 07:41:50 -0400 (EDT) Received: by mail-wm0-f69.google.com with SMTP id a77so12955744wma.12 for ; Mon, 29 May 2017 04:41:49 -0700 (PDT) Received: from mail-wm0-f65.google.com (mail-wm0-f65.google.com. [74.125.82.65]) by mx.google.com with ESMTPS id m133si11664898wma.86.2017.05.29.04.41.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 May 2017 04:41:48 -0700 (PDT) Received: by mail-wm0-f65.google.com with SMTP id d127so17076917wmf.1 for ; Mon, 29 May 2017 04:41:48 -0700 (PDT) From: Michal Hocko Subject: [PATCH 0/2] remove CONFIG_MOVABLE_NODE Date: Mon, 29 May 2017 13:41:38 +0200 Message-Id: <20170529114141.536-1-mhocko@kernel.org> Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Morton Cc: linux-mm@kvack.org, Mel Gorman , Vlastimil Babka , Andrea Arcangeli , Jerome Glisse , 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 Hi, this has been previously posted as an RFC [1]. As it hasn't met any disagreement, I have integrated the feedback and resending it without RFC and hope for a soon merging (ideally along with other memory hotplug pile). I am continuing to cleanup the memory hotplug code and CONFIG_MOVABLE_NODE seems dubious at best. The following two patches simply removes the flag and make it de-facto always enabled. The current semantic of the config option is twofold 1) it automatically binds hotplugable nodes to have memory in zone_movable by default when movable_node is enabled 2) forbids memory hotplug to online all the memory as movable when !CONFIG_MOVABLE_NODE. The later restriction is quite dubious because there is no clear cut of how much normal memory do we need for a reasonable system operation. A single memory block which is sufficient to allow further movable onlines is far from sufficient (e.g a node with >2GB and memblocks 128MB will fill up this zone with struct pages leaving nothing for other allocations). Removing the config option will not only reduce the configuration space it also removes quite some code. The semantic of the movable_node command line parameter is preserved. The first patch removes the restriction mentioned above and the second one simply removes all the CONFIG_MOVABLE_NODE related stuff. The last patch moves movable_node flag handling to memory_hotplug proper where it belongs. [1] http://lkml.kernel.org/r/20170524122411.25212-1-mhocko@kernel.org Shortlog Michal Hocko (3): mm, memory_hotplug: drop artificial restriction on online/offline mm, memory_hotplug: drop CONFIG_MOVABLE_NODE mm, memory_hotplug: move movable_node to the hotplug proper Diffstat: Documentation/admin-guide/kernel-parameters.txt | 7 ++- drivers/base/node.c | 4 -- include/linux/memblock.h | 25 ---------- include/linux/memory_hotplug.h | 10 ++++ include/linux/nodemask.h | 4 -- mm/Kconfig | 26 ---------- mm/memblock.c | 3 -- mm/memory_hotplug.c | 64 ++----------------------- mm/page_alloc.c | 2 - 9 files changed, 19 insertions(+), 126 deletions(-) -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org