From: Thomas Gleixner <tglx@linutronix.de>
To: Vikas Shivappa <vikas.shivappa@linux.intel.com>
Cc: vikas.shivappa@intel.com, tony.luck@intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
peterz@infradead.org, ravi.v.shankar@intel.com,
fenghua.yu@intel.com, andi.kleen@intel.com, davidcc@google.com,
eranian@google.com
Subject: Re: [PATCH 1/1] x86/cqm: Cqm requirements
Date: Tue, 7 Mar 2017 20:31:43 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703072011080.4299@nanos> (raw)
In-Reply-To: <1488908964-30261-1-git-send-email-vikas.shivappa@linux.intel.com>
On Tue, 7 Mar 2017, Vikas Shivappa wrote:
> Sending the cqm requirements as per Thomas comments in the previous
> verson of cqm patch series -
> https://marc.info/?l=linux-kernel&m=148374167726502
>
> This is modified version of requirements sent by Tony in the same
> thread with inputs from David and Stephan.
>
> Reviewed-by: Tony Luck<tony.luck@intel.com>
> Reviewed-by: David Carrillo-Cisneros <davidcc@google.com>
> Reviewed-by: Yu Fenghua <fenghua.yu@intel.com>
> Reviewed-by: Stephane Eranian <eranian@google.com>
> Signed-off-by: Vikas Shivappa <vikas.shivappa@linux.intel.com>
That's all nice and good, but I still have no coherent explanation why
measuring across allocation domains makes sense.
Repeating this requirement w/o explanation does not get us anywhere.
For the record:
I can understand the use case for bandwidth, but that's a pretty trivial
act of summing it up in software, so there is no actual requirement to do
that with a seperate RMID.
For cache oocupancy it still does not make any sense unless there is some
magic voodoo I'm not aware of to decipher the meaning of those numbers.
Thanks,
tglx
next prev parent reply other threads:[~2017-03-07 20:12 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 [this message]
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
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.1703072011080.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®