| 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
| ||
|
Date: Thu, 20 Mar 2008 12:03:16 -0400 From: Jon Masters <jcm@...hat.com> To: linux-kernel@...r.kernel.org Cc: Jeff Burke <jburke@...hat.com> Subject: CPU siblings Yo, Myself and a colleague were just discussing the output of /proc/cpuinfo, specifically the CPU siblings field. He pointed out/we think that this historically was supposed to be number of HT siblings for a given CPU. The actual value of that field comes from the Hamming Weight (number of set bits) of the per_cpu cpu_core_map variable, which supposedly is "representing HT and core siblings of each logical CPU", i.e. both HT siblings and additional cores within the same CPU package. Does this mean that "siblings" needs renaming? (doesn't it come originally from "HT siblings"? or is it supposed to be both?). More importantly, what's the correct way to determine number of HTs? Jon. -- 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