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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87my45yk79.fsf@basil.nowhere.org>
Date:	Mon, 05 Oct 2009 16:44:10 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Tejun Heo <tj@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: use near online node instead of round bin for numa

Yinghai Lu <yinghai@...nel.org> writes:

> cpu to node mapping is set in following sequence:
> 1. numa_init_array: set up roundbin from cpu to online node
> 2. init_cpu_to_node: set that according to apicid_to_node[] according to srat
> 		  only handle that node is online, and leave other cpu on node
> 		  without ram (aka not online) to still round-bin
> 3. later srat_detect_node for intel/amd, will use first_online node or near by
>    node.
>
> problem is that setup_per_cpu_areas() is called between  2 and 3. the per_cpu
> for cpu on node with ram is on different node. and could put that on node with
> two hops away.
>
> so try add find_near_online_node() and call int init_cpu_to_node()

This fallback case should not really happen anyways, unless the BIOS is buggy
(in this case it might better to completely reject the SRAT because
more might be wrong).

Do you have a system where this is needed?

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ