From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: jschopp@austin.ibm.com, haveblue@us.ibm.com
Cc: Andrew Morton <akpm@osdl.org>,
ak@suse.de, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH: 003/017](RFC) Memory hotplug for new nodes v.3.(get node id at probe memory)
Date: Tue, 14 Mar 2006 20:40:25 +0900 [thread overview]
Message-ID: <20060314201603.9159.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20060310154600.CA73.Y-GOTO@jp.fujitsu.com>
> > Yasunori Goto <y-goto@jp.fujitsu.com> wrote:
> > >
> > > When CONFIG_NUMA && CONFIG_ARCH_MEMORY_PROBE, nid should be defined
> > > before calling add_memory_node(nid, start, size).
> > >
> > > Each arch , which supports CONFIG_NUMA && ARCH_MEMORY_PROBE, should
> > > define arch_nid_probe(paddr);
> > >
> > > Powerpc has nice function. X86_64 has not.....
> >
> > This patch uses an odd mixture of __devinit and <nothing-at-all> in
> > arch/x86_64/mm/init.c. I guess it should be using __meminit
> > throughout.
>
> Oh... I made mistake. I'll fix them.
Hmmm. I'm confusing again about this. :-(
Dave-san, Joel-san.
Why does Powerpc use __devinit for add_memory()?
Usually, add_memory() is never called at boottime.
So, I suppose __meminit nor __devinit is not needed at all around here.
But, does it have a plan that add_memory() is called only boottime on
Powerpc?
--
Yasunori Goto
--
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-03-14 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 13:41 Yasunori Goto
2006-03-09 12:00 ` Andrew Morton
2006-03-10 8:05 ` Yasunori Goto
2006-03-14 11:40 ` Yasunori Goto [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=20060314201603.9159.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=jschopp@austin.ibm.com \
--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