Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751251Ab3JAFqx (ORCPT ); Tue, 1 Oct 2013 01:46:53 -0400 Received: from mail-ee0-f46.google.com ([74.125.83.46]:37790 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751008Ab3JAFqv (ORCPT ); Tue, 1 Oct 2013 01:46:51 -0400 Date: Tue, 1 Oct 2013 07:46:46 +0200 From: Ingo Molnar To: Zhang Yanfei Cc: Andrew Morton , "H. Peter Anvin" , Tejun Heo , Lai Jiangshan , Wen Congyang , isimatu.yasuaki@jp.fujitsu.com, izumi.taku@jp.fujitsu.com, Zhang Yanfei , Tang Chen , linux-doc@vger.kernel.org, "linux-kernel@vger.kernel.org" , Linux MM , imtangchen@gmail.com Subject: Re: [PATCH -mm] mm, memory-hotpulg: Rename movablenode boot option to movable_node Message-ID: <20131001054646.GA17220@gmail.com> References: <5249B7C6.7010902@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5249B7C6.7010902@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1412 Lines: 32 * Zhang Yanfei wrote: > @@ -153,11 +153,18 @@ config MOVABLE_NODE > help > Allow a node to have only movable memory. Pages used by the kernel, > such as direct mapping pages cannot be migrated. So the corresponding > + memory device cannot be hotplugged. This option allows the following > + two things: > + - When the system is booting, node full of hotpluggable memory can > + be arranged to have only movable memory so that the whole node can > + be hotplugged. (need movable_node boot option specified). So this is _exactly_ what I complained about earlier: why is the movable_node boot option needed to get that extra functionality? It's clearly not just a drop-in substitute to CONFIG_MOVABLE_NODE but extends its functionality, right? Boot options are _very_ poor user interface. If you don't want to enable it by default then turn this sub-functionality into CONFIG_MOVABLE_NODE_AUTO and keep it default-off - but don't pretend that this is only about CONFIG_MOVABLE_NODE alone - it isnt: as described above the 'movable_node' is needed for the full functionality to be available! Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/