linux-kernel - Re: [PATCH] x86: new topology for multi-NUMA-node CPUs

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:	Fri, 19 Sep 2014 13:45:29 +0200
From:	Karel Zak <kzak@...hat.com>
To:	Dave Hansen <dave@...1.net>
Cc:	linux-kernel@...r.kernel.org, dave.hansen@...ux.intel.com,
	a.p.zijlstra@...llo.nl, mingo@...nel.org, hpa@...ux.intel.com,
	brice.goglin@...il.com, bp@...en8.de
Subject: Re: [PATCH] x86: new topology for multi-NUMA-node CPUs

On Thu, Sep 18, 2014 at 12:33:34PM -0700, Dave Hansen wrote:
> The sysfs effects here cause an issue with the hwloc tool where
> it gets confused and thinks there are more sockets than are
> physically present.
> 
> Before this patch, there are two packages:
> 
> # cd /sys/devices/system/cpu/
> # cat cpu*/topology/physical_package_id | sort | uniq -c
>      18 0
>      18 1
> 
> But 4 _sets_ of core siblings:
> 
> # cat cpu*/topology/core_siblings_list | sort | uniq -c
>       9 0-8
>       9 18-26
>       9 27-35
>       9 9-17
> 
> After this set, there are only 2 sets of core siblings, which
> is what we expect for a 2-socket system.
> 
> # cat cpu*/topology/physical_package_id | sort | uniq -c
>      18 0
>      18 1
> # cat cpu*/topology/core_siblings_list | sort | uniq -c
>      18 0-17
>      18 18-35

 hmm... it would be also nice to test it with lscpu(1) from 
 util-linux (but it uses maps rather than lists from cpu*/topology/).

    Karel

-- 
 Karel Zak  <kzak@...hat.com>
 http://karelzak.blogspot.com
--
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/