[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190226185358.GQ2861@worktop.programming.kicks-ass.net>
Date: Tue, 26 Feb 2019 19:53:58 +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:
> Added sysfs package_threads, package_threads_list
>
> Added this attribute to show threads siblings in a package.
> Exactly same as "core_siblings above", a name now deprecated.
> This attribute name and definition is immune to future
> topology changes.
>
> Suggested by Brice.
>
> Added sysfs die_threads, die_threads_list
>
> Added this attribute to show which threads siblings in a die.
> V1 had proposed putting this info into "core_siblings", but we
> decided to leave that legacy attribute alone.
> This attribute name and definition is immune to future
> topology changes.
>
> On a single die-package system this attribute has same contents
> as "package_threads".
>
> Suggested by Brice.
>
> Added sysfs core_threads, core_threads_list
>
> Added this attribute to show which threads siblings in a core.
> Exactly same as "thread_siblings", a name now deprecated.
> This attribute name and definition is immune to future
> topology changes.
>
> Suggested by Brice.
I think I prefer 's/threads/cpus/g' on that. Threads makes me think SMT,
and I don't think there's any guarantee the part in question will have
SMT on.
Powered by blists - more mailing lists