linux-kernel - Re: [PATCH 0/14] v2 multi-die/package topology support

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: <20190226185131.GP2861@worktop.programming.kicks-ass.net>
Date:   Tue, 26 Feb 2019 19:51:31 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Len Brown <lenb@...nel.org>
Cc:     x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/14] v2 multi-die/package topology support

On Tue, Feb 26, 2019 at 01:19:58AM -0500, Len Brown wrote:
> Restored sysfs core_siblings, core_siblings_list
> 
> 	v1 proposed re-defining this existing attribute to
> 	be the threads in a die, rather than in a package.
> 
> 	For compatibility, decided rather to keep this
> 	attribute unchanged, for now, even though
> 	its name makes little sense, and it makes
> 	no sense in a multi-die system.

So why do things that make no sense? What breaks?