From: Arnd Bergmann <arnd@arndb.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Martin Bligh <mbligh@mbligh.org>,
Christian Krafft <krafft@de.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 2/2] enables booting a NUMA system where some nodes have no memory
Date: Thu, 16 Nov 2006 01:26:01 +0100 [thread overview]
Message-ID: <200611160126.02016.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0611151440400.23201@schroedinger.engr.sgi.com>
On Wednesday 15 November 2006 23:41, Christoph Lameter wrote:
> On Wed, 15 Nov 2006, Martin Bligh wrote:
> > A node is an arbitrary container object containing one or more of:
> >
> > CPUs
> > Memory
> > IO bus
+ SPUs on a Cell processor
> > It does not have to contain memory.
>
> I have never seen a node on Linux without memory. I have seen nodes
> without processors and without I/O but not without memory.This seems to be
> something new?
In this particular case, we have a dual-socket Cell/B.E. blade server,
where each of the two CPU-socket/south-bridge/memory combinations is
treated as a separate node. The two points that make this tricky
are:
- we want to be able to boot with the 'mem=512M' option, which effectively
disables the memory on the second node (each node has 512MiB).
- Each node has 8 SPUs, all of which we want to use. In order to use an
SPU, we call __add_pages to register the local memory on it, so we have
struct page pointers we can hand out to user mappings with ->nopage().
The __add_pages call needs to do node local allocations (there are
probably more allocations that have the same problem, but this is the
first one that crashes), which oops when there is no memory registered
at all for that node, instead of returning an error or falling back
on a non-local allocation.
Arnd <><
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-11-16 0:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 18:30 [patch 0/2] fix bugs while booting on NUMA system where some nodes have no mem Christian Krafft
2006-11-15 18:32 ` [patch 1/2] fix call to alloc_bootmem after bootmem has been freed Christian Krafft
2006-11-21 16:55 ` Andrew Morton
2006-11-21 18:02 ` Christian Krafft
2006-11-21 18:26 ` Andrew Morton
2006-11-22 9:23 ` Arnd Bergmann
2006-11-15 18:34 ` [patch 2/2] enables booting a NUMA system where some nodes have no memory Christian Krafft
2006-11-15 21:24 ` Christoph Lameter
2006-11-15 21:58 ` Jack Steiner
2006-11-15 22:40 ` Christoph Lameter
2006-11-15 22:43 ` Martin Bligh
2006-11-15 22:52 ` Christoph Lameter
2006-11-16 0:54 ` KAMEZAWA Hiroyuki
2006-11-16 0:57 ` Christoph Lameter
2006-11-16 1:17 ` KAMEZAWA Hiroyuki
2006-11-16 15:40 ` Christian Krafft
2006-11-16 15:49 ` Martin J. Bligh
2006-11-16 18:46 ` Christoph Lameter
2006-11-16 2:01 ` Martin Bligh
2006-11-16 1:35 ` Jack Steiner
2006-11-16 1:57 ` Christoph Lameter
2006-11-16 2:09 ` Martin Bligh
2006-11-16 2:35 ` Christoph Lameter
2006-11-16 3:28 ` Jack Steiner
2006-11-15 22:05 ` Martin Bligh
2006-11-15 22:41 ` Christoph Lameter
2006-11-15 22:46 ` Martin Bligh
2006-11-15 22:51 ` Christoph Lameter
2006-11-16 0:59 ` KAMEZAWA Hiroyuki
2006-11-16 1:22 ` Yasunori Goto
2006-11-16 0:26 ` Arnd Bergmann [this message]
2006-11-16 0:45 ` Christoph Lameter
2006-11-16 13:08 ` Arnd Bergmann
2006-11-16 0:44 ` Jesper Juhl
2006-11-16 0:46 ` Christoph Lameter
2006-11-16 15:21 ` Lee Schermerhorn
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=200611160126.02016.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=clameter@sgi.com \
--cc=krafft@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.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