From: Thomas Gleixner <tglx@linutronix.de>
To: David Carrillo-Cisneros <davidcc@google.com>
Cc: Stephane Eranian <eranian@google.com>,
"Luck, Tony" <tony.luck@intel.com>,
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>
Subject: Re: [PATCH 1/1] x86/cqm: Cqm requirements
Date: Thu, 9 Mar 2017 12:01:14 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703091145070.3521@nanos> (raw)
In-Reply-To: <CALcN6mgs=_wkav=reLsYOQW1N9Na=x9xKmM5GWvh4=0n_XD3Ng@mail.gmail.com>
On Wed, 8 Mar 2017, David Carrillo-Cisneros wrote:
> On Wed, Mar 8, 2017 at 12:30 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > Same applies for per CPU measurements.
>
> For CPU measurements. We need perf-like CPU filtering to support tools
> that perform low overhead monitoring by polling CPU events. These
> tools approximate per-cgroup/task events by reconciling CPU events
> with logs of what job run when in what CPU.
Sorry, but for CQM that's just voodoo analysis. Lets look at an example:
CPU default is CAT group 0 (20% of cache)
T1 belongs to CAT group 1 (40% of cache)
T2 belongs to CAT group 2 (40% of cache)
Now you do low overhead samples of the CPU (all groups accounted) with 1
second period.
Lets assume that T1 runs 50% and T2 runs 20% the rest of the time is
utilized by random other things and the kernel itself (using CAT group 0).
What is the accumulated value telling you?
How do you approximate that back to T1/T2 and the rest?
How do you do that when the tasks are switching between the samples several
times?
I really have idea how that should work and what the value of this would
be.
Thanks,
tglx
next prev parent reply other threads:[~2017-03-09 11:02 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
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 [this message]
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.1703091145070.3521@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®