From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 06 Sep 2008 16:06:38 +0900 From: Yasunori Goto Subject: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option In-Reply-To: <20080906000154.GC18288@one.firstfloor.org> References: <20080905215452.GF11692@us.ibm.com> <20080906000154.GC18288@one.firstfloor.org> Message-Id: <20080906153855.7260.E1E9C6FF@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Andi Kleen Cc: Gary Hade , linux-mm@kvack.org, Andrew Morton , Badari Pulavarty , Mel Gorman , Chris McDermott , linux-kernel@vger.kernel.org, x86@kernel.org, Ingo Molnar List-ID: > > I am not sure if I understand why you appear to be opposed to > > enabling the hotremove function before all the issues related > > I'm quite sceptical that it can be ever made to work in a useful > way for real hardware (as opposed to an hypervisor para virtual setup > for which this interface is not the right way -- it should be done > in some specific driver instead) > And if it cannot be made to work then it will be a false promise > to the user. They will see it and think it will work, but it will > not. > > This means I don't see a real use case for this feature. I don't think its driver is almighty. IIRC, balloon driver can be cause of fragmentation for 24-7 system. In addition, I have heard that memory hotplug would be useful for reducing of power consumption of DIMM. I have to admit that memory hotplug has many issues, but I would like to solve them step by step. Thanks. -- Yasunori Goto -- 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