linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: y-goto@jp.fujitsu.com, akpm@osdl.org, tony.luck@intel.com,
	ak@suse.de, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH: 002/017]Memory hotplug for new nodes v.4.(change name old add_memory() to arch_add_memory())
Date: Sat, 18 Mar 2006 10:26:53 +0900	[thread overview]
Message-ID: <20060318102653.57c6a2af.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1142615538.10906.67.camel@localhost.localdomain>

Hi,
On Fri, 17 Mar 2006 09:12:18 -0800
Dave Hansen <haveblue@us.ibm.com> wrote:

> On Fri, 2006-03-17 at 17:20 +0900, Yasunori Goto wrote:
> > This patch changes name of old add_memory() to arch_add_memory.
> > and use node id to get pgdat for the node at NODE_DATA().
> > 
> > Note: Powerpc's old add_memory() is defined as __devinit. However,
> >       add_memory() is usually called only after bootup. 
> >       I suppose it may be redundant. But, I'm not sure about powerpc.
> >       So, I keep it. (But, __meminit is better than __devinit at least.)
> 
> My thoughts when originally designing the API were that the architecture
> may be the only bit that actually knows where the memory _is_.  So, we
> shouldn't involve the generic code in figuring this out.
> 
> You can see the result of this in the next patch because there is a new
> function introduced to hide the arch-specific node lookup.  If that was
> simply done in the already arch-specific add_memory() function, then you
> wouldn't need arch_nid_probe() and its related #ifdefs at all.
> 
If *determine node* function is moved to arch specific parts,
memory hot add need more and more codes to determine  paddr -> nid in arch
specific codes. Then, we have to add new paddr->nid function even if new nid is
passed by firmware. We *lose* useful information of nid from firmware if 
add_memory() has just 2 args, (start, end). 

Considering ACPI, ia64/x86_64 can share codes and it depends on ACPI , not on arch. 


It's trade-off between add special tiny #ifdef for probe
(not-firmware-supported memory hotplug) and add many codes for firmware-supported
memory hotplug function. Again, we *lose* information of nid from firmware 
if add_memory() has just 2 args (start, end). This is bad thing.

-- 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>

  reply	other threads:[~2006-03-18  1:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17  8:20 Yasunori Goto
2006-03-17 17:12 ` Dave Hansen
2006-03-18  1:26   ` KAMEZAWA Hiroyuki [this message]
2006-03-21 18:00     ` Dave Hansen
2006-03-22  0:05       ` KAMEZAWA Hiroyuki
2006-03-22  1:08         ` Dave Hansen
2006-03-22  1:38           ` KAMEZAWA Hiroyuki
2006-03-22  6:06             ` Yasunori Goto

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=20060318102653.57c6a2af.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tony.luck@intel.com \
    --cc=y-goto@jp.fujitsu.com \
    /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