From: Andi Kleen <ak@suse.de>
To: Matt Tolentino <metolent@cs.vt.edu>
Cc: akpm@osdl.org, discuss@x86-64.org, kmannth@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2/2] add x86-64 support for memory hot-add
Date: Mon, 9 Jan 2006 16:36:20 +0100 [thread overview]
Message-ID: <200601091636.21118.ak@suse.de> (raw)
In-Reply-To: <200601091521.k09FLU1t022321@ap1.cs.vt.edu>
On Monday 09 January 2006 16:21, Matt Tolentino wrote:
> Add x86-64 specific memory hot-add functions, Kconfig options,
> and runtime kernel page table update functions to make
> hot-add usable on x86-64 machines. Also, fixup the nefarious
> conditional locking and exports pointed out by Andi.
I'm trying to stabilize my tree for the 2.6.16 submission right now
and this one comes a bit too late and is a bit too involved
to slip through - sorry. I will consider it after Linus
has merged the whole batch of changes for 2.6.16 - so hopefully
in 2.6.17.
> +/*
> + * Memory hotplug specific functions
> + * These are only for non-NUMA machines right now.
How much work would it be to allow it for NUMA kernels too?
-Andi
next prev parent reply other threads:[~2006-01-09 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 15:21 [patch 2/2] add x86-64 support for memory hot-add Matt Tolentino
2006-01-09 15:36 ` Andi Kleen [this message]
2006-01-09 18:51 ` Yinghai Lu
2006-01-09 19:24 ` keith
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 19:28 Lu, Yinghai
2006-01-09 19:37 ` Andi Kleen
2006-01-09 19:29 Lu, Yinghai
2006-01-09 19:55 Tolentino, Matthew E
2006-01-09 20:09 ` keith
2006-01-10 12:34 ` Yasunori Goto
2006-01-10 12:43 ` Yasunori Goto
2006-01-10 12:48 ` Andi Kleen
2006-01-11 1:49 ` Yasunori Goto
2006-01-09 20:27 ` Andi Kleen
2006-01-09 19:58 Tolentino, Matthew E
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=200601091636.21118.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=kmannth@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=metolent@cs.vt.edu \
/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;
as well as URLs for NNTP newsgroup(s).