From: Andi Kleen <andi@firstfloor.org>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RESEND] x86: add memory hotremove config option
Date: 03 Nov 2008 16:22:27 +0100 [thread overview]
Message-ID: <m0od0wzvf0.fsf@localhost.localdomain> (raw)
In-Reply-To: <20081031175203.GA7483@us.ibm.com>
Gary Hade <garyhade@us.ibm.com> writes:
>
> Memory hotremove functionality can currently be configured into
> the ia64, powerpc, and s390 kernels. This patch makes it possible
> to configure the memory hotremove functionality into the x86
> kernel as well.
You still didn't say how this is actually going to work and what
it is good for? See thread last time. The big difference is that
the powerpc and s390 kernels have the needed Hypervisor interfaces, x86
has not (not sure about ia64)
iirc the code is useless for hardware based memory hotplug (because it
doesn't free full nodes) and not useful for hypervisor based memory
hotplug without additional drivers (and actual hypervisor support of
course)
Enabling the sysfs interface now is just giving a promise to the user
that you cannot hold. Also it makes the kernel bigger without actually
giving useful functionality.
If some x86 hypervisor gains support for this I think the interface
shouldn't be through sysfs, but controlled through the respective PV drivers
which need to be involved anyways.
-Andi
--
ak@linux.intel.com
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-11-03 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 17:52 Gary Hade
2008-11-03 9:03 ` Ingo Molnar
2008-11-03 15:22 ` Andi Kleen [this message]
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=m0od0wzvf0.fsf@localhost.localdomain \
--to=andi@firstfloor.org \
--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