From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: PXM/Nid/SLIT patch
Date: Wed, 18 Feb 2004 19:04:30 +0000 [thread overview]
Message-ID: <20040218190430.GM13235@sgi.com> (raw)
In-Reply-To: <40321CF7.5020301@hp.com>
On Wed, Feb 18, 2004 at 10:59:03AM -0800, David Mosberger wrote:
> Christoph> but honestly can't you fix the firmware to return sane
> Christoph> information instead? i.e. move the above fix to firmware
> Christoph> instead of letting linux fixup the reported data.
>
> Hmmh, I'm no NUMA-expert and it isn't clear to me whether the patch is
> working around a firmware-bug or a limitation in the Linux NUMA code.
> I don't see off-hand why it should be illegal to have a memory config
> with only one node with memory. The whole PXM_MAGIC business looks
> strange to me though. Can someone explain?
Well, it would be nice if memory layout was reported fully, with the
correct CPU/node and memory affinity information. That would allow us
to either interleave in software (maybe a new flag that changes the way
discontig.c builds the memory maps) or just treat the machine as a
normal NUMA box. But maybe this isn't possible with the HP cell boxes?
Robert, maybe you can describe the memory layout of these machines a
little more (sorry if I missed some discussion, I'm having mail trouble
right now and was unsubscribed from linux-ia64).
Thanks,
Jesse
next prev parent reply other threads:[~2004-02-18 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 13:53 PXM/Nid/SLIT patch Robert Picco
2004-02-17 22:32 ` Jesse Barnes
2004-02-18 15:33 ` Robert Picco
2004-02-18 17:08 ` Christoph Hellwig
2004-02-18 18:56 ` Robert Picco
2004-02-18 18:59 ` David Mosberger
2004-02-18 19:04 ` Jesse Barnes [this message]
2004-02-18 19:06 ` Jesse Barnes
2004-02-18 19:13 ` Christoph Hellwig
2004-02-18 19:19 ` Robert Picco
2004-02-18 19:36 ` Jesse Barnes
2004-02-18 19:43 ` David Mosberger
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=20040218190430.GM13235@sgi.com \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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