linux-kernel - Re: [PATCH 14/16] x86: Unify CPU -> NUMA node mapping between 32 and 64bit

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:	Thu, 9 Dec 2010 22:49:02 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Tejun Heo <tj@...nel.org>
cc:	linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
	x86@...nel.org, eric.dumazet@...il.com, yinghai@...nel.org,
	brgerst@...il.com, gorcunov@...il.com, penberg@...nel.org
Subject: Re: [PATCH 14/16] x86: Unify CPU -> NUMA node mapping between 32
 and 64bit

On Sat, 27 Nov 2010, Tejun Heo wrote:

> Unlike 64bit, 32bit has been using its own cpu_to_node_map[] for CPU
> -> NUMA node mapping.  Replace it with early_percpu variable
> x86_cpu_to_node_map and share the mapping code with 64bit.
> 
> * USE_PERCPU_NUMA_NODE_ID is now enabled for 32bit too.
> 
> * x86_cpu_to_node_map and numa_set/clear_node() are moved from numa_64
>   to numa.  For now, x86_cpu_to_node_map is initialized with 0 instead
>   of NUMA_NO_NODE.  This is to avoid introducing unexpected behavior

That's true for 32bit only, right? I actually had to dig into the code
to verify this. Please make this clear for the casual reader.

Thanks,

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