From: Andi Kleen <andi@firstfloor.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Christoph Lameter <clameter@sgi.com>,
bob.picco@hp.com
Subject: Re: [RFC] [PATCH] more support for memory-less-node.
Date: Tue, 13 Feb 2007 09:29:49 +0100 [thread overview]
Message-ID: <200702130929.49349.andi@firstfloor.org> (raw)
In-Reply-To: <20070213155736.1131d46a.kamezawa.hiroyu@jp.fujitsu.com>
> In my understanding, a "node" is a block of cpu, memory, devices.
> and there could be cpu-only-node, memory-only-node, device-only-node...
The trouble with this is that you'll need to harden large parts
of code against these. Especially a NULL pgdat is something quite
dangerous. You could make it a dummy empty pgdat, but just assigning it
nearby seems easier.
-Andi
next prev parent reply other threads:[~2007-02-13 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 6:57 [RFC] [PATCH] more support for memory-less-node KAMEZAWA Hiroyuki
2007-02-13 8:29 ` Andi Kleen [this message]
2007-02-13 8:38 ` KAMEZAWA Hiroyuki
2007-02-13 17:25 ` Christoph Lameter
2007-02-14 0:12 ` KAMEZAWA Hiroyuki
2007-02-13 17:24 ` Christoph Lameter
2007-02-13 17:09 ` Martin J. Bligh
2007-02-13 17:45 ` Andi Kleen
2007-02-13 18:03 ` Christoph Lameter
2007-02-13 18:16 ` Martin J. Bligh
2007-02-13 18:50 ` Christoph Lameter
2007-02-14 0:20 ` KAMEZAWA Hiroyuki
2007-02-13 18:11 ` Martin J. Bligh
2007-02-13 18:18 ` Andi Kleen
2007-02-13 18:26 ` Martin J. Bligh
2007-02-13 18:51 ` Bob Picco
[not found] <7NZO0-6et-1@gated-at.bofh.it>
[not found] ` <7Oa6N-5If-3@gated-at.bofh.it>
[not found] ` <7Oaq4-6ow-7@gated-at.bofh.it>
[not found] ` <7Oaq6-6ow-17@gated-at.bofh.it>
2007-02-15 12:21 ` Bodo Eggert
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=200702130929.49349.andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=bob.picco@hp.com \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.