From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: PXM/Nid/SLIT patch
Date: Wed, 18 Feb 2004 19:36:48 +0000 [thread overview]
Message-ID: <20040218193648.GP13235@sgi.com> (raw)
In-Reply-To: <40321CF7.5020301@hp.com>
On Wed, Feb 18, 2004 at 02:19:23PM -0500, Robert Picco wrote:
> Our HP default boot configuration has all memory interleaved and
> reported in NUMA SRAT PXM 255. The
> other cell nodes (PXMs) don't have any memory. This was totally
> unexpected by the current NUMA code. There will be N-1 nids with CPUs
> and no memory and 1 NID with all the memory. Initialization crashes
> very early. The current code expects each node to have local memory.
Oh, right, there's that... we could fix it to fallback to other nodes
though. In fact, we should do the bootmem initialization earlier and
use alloc_bootmem_node for things instead of allocating stuff in
find_pernode_space. If we fixed that your machine would work pretty
well I think.
> So, if we had a tool to configure CLM for all cells, there would be N-1
> nids with CPU and local memory and 1 nid with just interleaved memory.
> The current kernel code would work fine but the SLIT information would be
> wrong because PXM 255 isn't reported by the firmware in the SLIT table.
> numa_slit isn't used by non-machine dependent code for memory
> allocation policy but could be in the future for memory allocations
> when the current node's memory is exhausted. numa_slit would be used as
> a measure of the best locality to make the allocation from (shortest path).
No, pgdat->zonelist is used instead. It needs to be built better
though...
Jesse
next prev parent reply other threads:[~2004-02-18 19:36 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
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 [this message]
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=20040218193648.GP13235@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