Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261525AbVBRVxB (ORCPT ); Fri, 18 Feb 2005 16:53:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261528AbVBRVxA (ORCPT ); Fri, 18 Feb 2005 16:53:00 -0500 Received: from mx1.redhat.com ([66.187.233.31]:28586 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S261525AbVBRVws (ORCPT ); Fri, 18 Feb 2005 16:52:48 -0500 Date: Fri, 18 Feb 2005 16:52:25 -0500 (EST) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Dave Hansen cc: Linux Kernel Mailing List , lhms , linux-mm , Andy Whitcroft Subject: Re: [RFC][PATCH] Memory Hotplug In-Reply-To: <1108685111.6482.40.camel@localhost> Message-ID: References: <1108685033.6482.38.camel@localhost> <1108685111.6482.40.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; format=flowed Content-ID: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 27 On Thu, 17 Feb 2005, Dave Hansen wrote: > The attached patch is a prototype implementation of memory hot-add. It > allows you to boot your system, and add memory to it later. Why would > you want to do this? I want it so I can grow Xen guests after they have been booted up. Being able to hot-add memory is essential for dynamically resizing the memory of various guest OSes, to readjust them for the workload. Memory hot-remove isn't really needed with Xen, the balloon driver takes care of that. > I can post individual patches if anyone would like to comment on them. I'm interested. I want to get this stuff working with Xen ;) -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/