linux-kernel - Re: [BUG][PATCH] fix mempolcy's check on a system with memory-less-node take2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070208002428.1b7aa485.akpm@linux-foundation.org>
Date:	Thu, 8 Feb 2007 00:24:28 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andi Kleen <ak@...e.de>
Cc:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	LKML <linux-kernel@...r.kernel.org>, clameter@....com,
	GOTO <y-goto@...fujitsu.com>
Subject: Re: [BUG][PATCH] fix mempolcy's check on a system with
 memory-less-node take2

On Thu, 8 Feb 2007 09:19:16 +0100 Andi Kleen <ak@...e.de> wrote:

> The reason we present nodes to user space is that we can tell the user
> where the memory is. You seem to try to promote it to some abstract entity
> beyond that, but that doesn't seem particularly fruitful to me. I think
> I prefer "down to earth" memory nodes.

Who said a node is all about memory?

A node is (often) a circuit board, with an edge connector, containing some,
all or even none of a) CPUs, b) memory and c) IO devices.

That is how a kernel should model and treat it, surely?  That's reality.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/