From: Borislav Petkov <bp@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <h.peter.anvin@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] cacheinfo: Introduce cache id
Date: Fri, 1 Jul 2016 20:29:21 +0200 [thread overview]
Message-ID: <20160701182921.GD4749@pd.tnic> (raw)
In-Reply-To: <20160701180034.GA19287@intel.com>
On Fri, Jul 01, 2016 at 11:00:35AM -0700, Luck, Tony wrote:
> For CAT we only need the IDs to be unique at each level. Our tentative
> syntax for the schema file for CAT looks like this (for a theoretical
> system supporting CAT in both L2 and L3 with two L3 caches and eight L2 caches)
>
> L3:id0=fff;id1=ff0
> L2:id0=3;id1=c;id2=30;id3=c0;id4=3;id5=c;id6=30;id7=c0
So wouldn't it be straightforward and natural to do the following
nomenclature (which basically suggests itself):
ID<level>.<num>
?
So that the ID hierarchy above is:
ID3.0 ID3.1
ID2.0 ID2.1 ID2.2 ID2.3 ... ID2.7
I don't know if that's useful though.
I mean, we have that info in the path anyway:
/sys/devices/system/cpu/cpu0/cache/index3/id = 0xfff
...
and so on.
Whatever you do, as long as the nomenclature is documented somewhere,
say Documentation/x86/topology.txt, for example, we should be fine.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-07-01 18:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 1:56 [PATCH] cacheinfo: Introduce cache id Fenghua Yu
2016-06-30 1:56 ` Fenghua Yu
2016-07-01 10:21 ` Borislav Petkov
2016-07-01 16:50 ` Luck, Tony
2016-07-01 17:27 ` Borislav Petkov
2016-07-01 18:00 ` Luck, Tony
2016-07-01 18:29 ` Borislav Petkov [this message]
2016-07-01 18:32 ` Yu, Fenghua
2016-07-01 18:40 ` Borislav Petkov
2016-07-01 19:08 ` Yu, Fenghua
2016-07-04 17:29 ` Borislav Petkov
2016-07-01 18:01 ` Yu, Fenghua
2016-07-01 18:35 ` Borislav Petkov
2016-07-01 19:24 ` Yu, Fenghua
2016-07-04 17:58 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160701182921.GD4749@pd.tnic \
--to=bp@suse.de \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.