linux-kernel - Re: [2.6.20][PATCH] fix mempolicy error check on a system with memory-less-node

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Feb 2007 19:49:09 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Andi Kleen <ak@...e.de>
Cc:	linux-kernel@...r.kernel.org, y-goto@...fujitsu.com,
	clameter@...r.sgi.com, akpm@...l.org
Subject: Re: [2.6.20][PATCH] fix mempolicy error check on a system with
 memory-less-node

On Wed, 7 Feb 2007 11:41:25 +0100
Andi Kleen <ak@...e.de> wrote:

> On Wednesday 07 February 2007 11:37, KAMEZAWA Hiroyuki wrote:
> > On Wed, 7 Feb 2007 11:19:02 +0100
> > Andi Kleen <ak@...e.de> wrote:
> > > You can also alias node numbers to solve this: just point multiple node numbers 
> > > to the same pgdat. For a memory less node this would be a nearby one.
> > > 
> > Hmm, interesting...the 'alias' means follwing ?
> 
> Yes.
> 
> > NODE_DATA(A) = pgdat_for_A
> > NODE_DATA(B) = pgdat_for_A // B is memory-less.
> > - NODE_DATA(B) is valid but B is not online.
> 
> Well it is online because A is. For all practical purposes
> it is A, just under a different name.
> 
> > ==
> > looks complicated..and we have to care /sys/devices/system/node handling.
> 
> x86-64 used to do that when it still only did 1:1 cpu<->memory mappings.
> I don't remember any problems with it.
> 

How for_each_online_node(nid) works ? it can handle alias-nid ?

==
	for_each_online_node(nid) {
		pgdat = NODE_DATA(nid);
==
This code never accesses pgdat_for_A twice ?

Thanks,
-Kame


-
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/