public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Andi Kleen <ak@suse.de>,
	"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
Cc: discuss@x86-64.org, "Brown, Len" <len.brown@intel.com>,
	naveen.b.s@intel.com, Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>,
	ACPI-ML <linux-acpi@vger.kernel.org>,
	Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [discuss] Re: [RFC:PATCH(003/003)] Memory add to onlined node. (ver. 2) (For x86_64)
Date: Thu, 09 Feb 2006 19:56:48 +0900	[thread overview]
Message-ID: <20060209195345.6D06.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <200602091141.44456.ak@suse.de>

> On Thursday 09 February 2006 10:50, Yasunori Goto wrote:
> 
> > Current code adds memory to ZONE_NORMAL like this.
> > But, ZONE_DMA32 is available on 2.6.15. So, I'm afraid there are
> > 2 types trouble.
> > 
> >   a) When new memory is added to < 4GB, this should be added to 
> >      Zone_DMA32.
> >      Are there any real machine which allow to add memory under
> >      4GB?
> 
> x86-64 machines usually use a continuous memory map 
> because Windows gets unhappy with too big memory holes (and even
> Linux is not completely troublefree for UP install kernels)  And for a small
> system this implies memory < 4GB.

Ah, Ok. Then, it is bug. :-P

> 
> >   b) If machine boots up with under 4GB memory, and new memory 
> >      is added to over 4GB, then kernel might panic due to Zone Normal's
> >      initialization is imcomplete.
> >   
> > Q2) 
> >   Are there any real machine which can add memory with NUMA feature?
> 
> There are and will be.

I see. I'll continue my job with x86_64 too. :-)

Thanks.

-- 
Yasunori Goto 



      reply	other threads:[~2006-02-09 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  7:06 [RFC:PATCH(003/003)] Memory add to onlined node. (ver. 2) (For x86_64) Yasunori Goto
2006-02-09  9:50 ` Yasunori Goto
2006-02-09 10:41   ` [discuss] " Andi Kleen
2006-02-09 10:56     ` 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=20060209195345.6D06.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=ak@suse.de \
    --cc=bjorn.helgaas@hp.com \
    --cc=discuss@x86-64.org \
    --cc=len.brown@intel.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.e.tolentino@intel.com \
    --cc=naveen.b.s@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