From: Rik van Riel <riel@redhat.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lhms <lhms-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [RFC][PATCH] Memory Hotplug
Date: Fri, 18 Feb 2005 16:52:25 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.61.0502181650381.4052@chimarrao.boston.redhat.com> (raw)
In-Reply-To: <1108685111.6482.40.camel@localhost>
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, 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: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-02-18 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 0:03 [RFC][PATCH] Sparse Memory Handling (hot-add foundation) Dave Hansen
2005-02-18 0:05 ` [RFC][PATCH] Memory Hotplug Dave Hansen
2005-02-18 21:52 ` Rik van Riel [this message]
2005-02-18 22:20 ` Dave Hansen
2005-02-19 1:48 ` Rik van Riel
2005-02-18 5:16 ` [RFC][PATCH] Sparse Memory Handling (hot-add foundation) Mike Kravetz
2005-02-18 15:31 ` Dave Hansen
2005-02-18 10:04 ` Andi Kleen
2005-02-18 15:42 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0502181650381.4052@chimarrao.boston.redhat.com \
--to=riel@redhat.com \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox