public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, Andi Kleen <ak@suse.de>,
	"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
	linux-ia64@vger.kernel.org,
	Linux Kernel ML <linux-kernel@vger.kernel.org>,
	Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>,
	x86-64 Discuss <discuss@x86-64.org>
Subject: Re: [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat all
Date: Sat, 11 Feb 2006 03:06:11 +0000	[thread overview]
Message-ID: <20060211120325.D358.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <1139588910.9209.73.camel@localhost.localdomain>

> On Fri, 2006-02-10 at 23:20 +0900, Yasunori Goto wrote:
> > +        unsigned long size = arch_pernode_size(nid); 
> 
> Size in what?  Pages?  Bytes?  Meters? :)

Do you mean variable name is not appropriate?

Then, I'll change it to pernode_size, pernode_struct_size or
something. :-)

-- 
Yasunori Goto 



  reply	other threads:[~2006-02-11  3:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 14:20 [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat allocation) Yasunori Goto
2006-02-10 16:26 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes Dave Hansen
2006-02-11  3:02   ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat all Yasunori Goto
2006-02-10 16:28 ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes Dave Hansen
2006-02-11  3:06   ` Yasunori Goto [this message]
2006-02-10 16:28 ` Dave Hansen
2006-02-10 16:30 ` Dave Hansen
2006-02-11  3:08   ` [Lhms-devel] [RFC/PATCH: 001/010] Memory hotplug for new nodes with pgdat allocation. (pgdat all 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=20060211120325.D358.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=haveblue@us.ibm.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.e.tolentino@intel.com \
    --cc=tony.luck@intel.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