From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: kmannth@us.ibm.com
Cc: lhms-devel@lists.sourceforge.net, linux-mm@kvack.org,
haveblue@us.ibm.com
Subject: Re: [RFC] Patch [2/4] x86_64 sparsmem add - implement arch_find_node in memory_hotplug code.
Date: Sat, 24 Jun 2006 16:24:21 +0900 [thread overview]
Message-ID: <20060624162421.bb3f1065.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1151114748.7094.51.camel@keithlap>
Hi,
On Fri, 23 Jun 2006 19:05:48 -0700
keith mannthey <kmannth@us.ibm.com> wrote:
> I intend to implement an arch_find_node for i386 in the near
> future.
>
ya, welcome :)
>
> Signed-off-by: Keith Mannthey <kmannth@us.ibm.com>
>
+config ARCH_FIND_NODE
+ def_bool y
+ depends on MEMORY_HOTPLUG
+
maybe
--
depends on MEMORY_HOTPLUG && NUMA
--
is better.
-Kame
--
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:[~2006-06-24 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 2:05 keith mannthey
2006-06-24 7:24 ` KAMEZAWA Hiroyuki [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=20060624162421.bb3f1065.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=haveblue@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--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