From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <ygoto@us.fujitsu.com>
Cc: keith <kmannth@us.ibm.com>,
external hotplug mem list <lhms-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>, Chris McDermott <lcm@us.ibm.com>
Subject: Re: [Lhms-devel] [RFC] fix for hot-add enabled SRAT/BIOS and numa KVA areas
Date: Wed, 17 Nov 2004 14:42:34 -0800 [thread overview]
Message-ID: <1100731354.12373.224.camel@localhost> (raw)
In-Reply-To: <20041117133315.92B7.YGOTO@us.fujitsu.com>
On Wed, 2004-11-17 at 14:33, Yasunori Goto wrote:
> But e820 probably indicates just memory areas which
> are already connected on the board, right?
It's more than that. It indicates which were connected the first time
that the machine was powered on. If you suspend or hibernate the system
for some reason, it has to always present the e820 as it initially
appeared.
> BTW, I have a question.
> - Can x445 be attached memory without removing the node?
> In my concern machine, there is no physical space to
> hot add or exchange memory without physical removing
> the node. But, this SRAT table indicate that
> all of proximity is 0x01....
> Or is it just logical attachment?
You can't remove nodes, just DIMMs. The x440 hotplug is more like the
SMP case that I've always been concerned with.
-- Dave
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-11-17 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 2:37 keith
2004-11-17 17:11 ` [Lhms-devel] " Dave Hansen
2004-11-18 2:08 ` keith
2004-11-18 2:24 ` Dave Hansen
2004-11-18 19:18 ` keith
2004-11-17 22:33 ` Yasunori Goto
2004-11-17 22:42 ` Dave Hansen [this message]
2004-11-17 23:21 ` Yasunori Goto
2004-11-18 2:18 ` keith
2004-11-18 2:16 ` keith
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=1100731354.12373.224.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=ygoto@us.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