From: Thomas Gleixner <tglx@linutronix.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Vikas Shivappa <vikas.shivappa@linux.intel.com>,
"Shivappa, Vikas" <vikas.shivappa@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>,
"davidcc@google.com" <davidcc@google.com>,
"eranian@google.com" <eranian@google.com>
Subject: RE: [PATCH 1/1] x86/cqm: Cqm requirements
Date: Tue, 7 Mar 2017 21:22:04 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703072119300.4299@nanos> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F6120F0A9@ORSMSX113.amr.corp.intel.com>
On Tue, 7 Mar 2017, Luck, Tony wrote:
> > That's all nice and good, but I still have no coherent explanation why
> > measuring across allocation domains makes sense.
>
> Is this in reaction to this one?
>
> >> 5) Put multiple threads into a single measurement group
>
> If we fix it to say "threads from the same CAT group" does it fix things?
>
> We'd like to have measurement groups use a single RMID ... if we
> allowed tasks from different CAT groups in the same measurement
> group we wouldn't be able to split the numbers back to report the
> right overall total for each of the CAT groups.
Right. And the same applies to CPU measurements. If we have threads from 3
CAT groups running on a CPU then the aggregate value (except for bandwidth
which can be computed by software) is useless.
Thanks,
tglx
next prev parent reply other threads:[~2017-03-07 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 17:49 Vikas Shivappa
2017-03-07 19:31 ` Thomas Gleixner
2017-03-07 20:04 ` Luck, Tony
2017-03-07 20:22 ` Thomas Gleixner [this message]
2017-03-07 23:29 ` Stephane Eranian
2017-03-07 23:31 ` Shivappa Vikas
2017-03-08 8:30 ` Thomas Gleixner
2017-03-08 17:58 ` David Carrillo-Cisneros
2017-03-09 11:01 ` Thomas Gleixner
2017-03-09 18:05 ` David Carrillo-Cisneros
2017-03-10 14:53 ` Thomas Gleixner
2017-03-11 1:53 ` David Carrillo-Cisneros
2017-03-13 19:10 ` Thomas Gleixner
2017-03-13 19:58 ` David Carrillo-Cisneros
2017-03-13 20:21 ` Thomas Gleixner
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=alpine.DEB.2.20.1703072119300.4299@nanos \
--to=tglx@linutronix.de \
--cc=andi.kleen@intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®