From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
Andi Kleen <ak@suse.de>
Cc: "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>,
x86-64 Discuss <discuss@x86-64.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [RFC:PATCH(003/003)] Memory add to onlined node. (ver. 2) (For x86_64)
Date: Thu, 09 Feb 2006 18:50:35 +0900 [thread overview]
Message-ID: <20060209164036.6CFC.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20060209153803.6CF4.Y-GOTO@jp.fujitsu.com>
BTW, I have 2 question about x86_64's memory hot-add.
Q1)
> int add_memory(u64 start, u64 size)
> {
> - struct pglist_data *pgdat = NODE_DATA(0);
> - struct zone *zone = pgdat->node_zones + MAX_NR_ZONES-2;
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?
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?
Or will be there?
In my patch, I assume that DSDT is defined well for NUMA by firmware.
(Container device, Memory device...).
But, if firmware doesn't define it, my patch is nonsense..
(Oh, I'm silly.....)
--
Yasunori Goto
next prev parent reply other threads:[~2006-02-09 9:52 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 [this message]
2006-02-09 10:41 ` [discuss] " Andi Kleen
2006-02-09 10:56 ` 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=20060209164036.6CFC.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