| 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
| ||
|
Message-ID: <4D029389.1050402@kernel.org> Date: Fri, 10 Dec 2010 21:54:33 +0100 From: Tejun Heo <tj@...nel.org> To: Thomas Gleixner <tglx@...utronix.de> 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 13/16] x86: Unify cpu/apicid <-> NUMA node mapping between 32 and 64bit On 12/10/2010 09:45 PM, Tejun Heo wrote: > I can change srat_detect_node() and nearby_node() to index by cpu but > as I have no idea what kind of broken configurations this is supposed > to deal with, I'm concerned that this may lead to different outcome by > walking the table in a different order. I can implement an apicid -> > numa node mapping function for this but this is something which is > inherently ugly, so maybe it's best to leave it ugly. Oh, right, another problem. It's possible that apicid <-> numa mapping exists when apicid <-> cpu doesn't. Again, this is a corner case which might not matter but I have no idea what kind of brokeness is being worked around and it would also be difficult to test whether the change is okay. If someone can tell me that this workaround can go away, it would be awesome. -- tejun -- 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