From: Andrew Morton <akpm@linux-foundation.org>
To: Andi Kleen <ak@suse.de>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>, GOTO <y-goto@jp.fujitsu.com>,
Christoph Lameter <clameter@engr.sgi.com>
Subject: Re: [2.6.20][PATCH] fix mempolicy error check on a system with memory-less-node
Date: Wed, 7 Feb 2007 09:43:44 -0800 [thread overview]
Message-ID: <20070207094344.0efdde10.akpm@linux-foundation.org> (raw)
In-Reply-To: <200702071750.55283.ak@suse.de>
On Wed, 7 Feb 2007 17:50:55 +0100 Andi Kleen <ak@suse.de> wrote:
> On Wednesday 07 February 2007 17:23, Andrew Morton wrote:
> > On 07 Feb 2007 11:20:06 +0100 Andi Kleen <ak@suse.de> wrote:
> >
> > > KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
> > >
> > > > current mempolicy just checks whether a node is online or not.
> > > > If there is memory-less-node, mempolicy's target node can be
> > > > invalid.
> > > > This patch adds a check whether a node has memory or not.
> > >
> > > IMHO there shouldn't be any memory less nodes. The architecture code
> > > should not create them. The CPU should be assigned to a nearby node instead.
> >
> > umm, why?
> >
> > A node which has CPUs and no memory is obviously physically possible and
> > isn't a completely insane thing for a user to do. I'd have thought that
> > the kernel should be able to cleanly and clearly handle it,
>
> It doesn't.
Fix it?
> > and to
> > accurately present the machine's topology to the user without us having to
> > go adding falsehoods like this?
>
> a node is a piece of memory. Without memory it doesn't make sense.
Who said? I can pick up a piece of circuitry which has four CPUs and no
RAM, wave it about then stick it in a computer. The kernel is just wrong,
surely?
next prev parent reply other threads:[~2007-02-07 17:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 11:23 [2.6.20][PATCH] fix mempolicy error check on a system with memory-less-node KAMEZAWA Hiroyuki
2007-02-06 17:26 ` Christoph Lameter
2007-02-07 1:14 ` KAMEZAWA Hiroyuki
2007-02-07 8:04 ` Christoph Lameter
2007-02-07 8:36 ` KAMEZAWA Hiroyuki
2007-02-08 11:49 ` Bob Picco
2007-02-07 10:20 ` Andi Kleen
2007-02-07 10:20 ` Andi Kleen
2007-02-07 10:07 ` KAMEZAWA Hiroyuki
2007-02-07 10:19 ` Andi Kleen
2007-02-07 10:37 ` KAMEZAWA Hiroyuki
2007-02-07 10:41 ` Andi Kleen
2007-02-07 10:49 ` KAMEZAWA Hiroyuki
2007-02-07 11:32 ` Andi Kleen
2007-02-07 12:27 ` KAMEZAWA Hiroyuki
2007-02-07 14:05 ` Christoph Lameter
2007-02-07 15:28 ` KAMEZAWA Hiroyuki
2007-02-07 14:03 ` Christoph Lameter
2007-02-07 16:23 ` Andrew Morton
2007-02-07 16:50 ` Andi Kleen
2007-02-07 17:43 ` Andrew Morton [this message]
2007-02-07 18:15 ` [PATCH] FS : Speedup rw_verify_area() Eric Dumazet
2007-02-08 0:37 ` [2.6.20][PATCH] fix mempolicy error check on a system with memory-less-node KAMEZAWA Hiroyuki
2007-02-08 19:09 ` Christoph Lameter
2007-02-08 19:26 ` Andrew Morton
2007-02-08 19:35 ` Christoph Lameter
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=20070207094344.0efdde10.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=clameter@engr.sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@jp.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