From: Matt Fleming <matt@console-pimps.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vikas Shivappa <vikas.shivappa@intel.com>,
Tejun Heo <tj@kernel.org>, "Auld, Will" <will.auld@intel.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Fleming, Matt" <matt.fleming@intel.com>,
h.peter.anvin@intel.com
Subject: Re: Cache Allocation Technology Design
Date: Thu, 6 Nov 2014 17:03:23 +0000 [thread overview]
Message-ID: <20141106170323.GJ3592@console-pimps.org> (raw)
In-Reply-To: <20141104131714.GR3219@twins.programming.kicks-ass.net>
On Tue, 04 Nov, at 02:17:14PM, Peter Zijlstra wrote:
>
> I don't like extending cpusets further. Its already a weird and too big
> controller.
>
> What is wrong with having a specific CQM controller and using it
> together with cpusets where desired?
The specific problem that conflating cpusets and the CAT controller is
trying to solve is that on some platforms the CLOS ID doesn't move with
data that travels up the cache hierarchy, i.e. we lose the CLOS ID when
data moves from LLC to L2.
I think the idea with pinning CLOS IDs to a specific cpu and any tasks
that are using that ID is that it works around this problem out of the
box, rather than requiring sysadmins to configure things.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-11-06 17:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 18:44 Cache Allocation Technology Design vikas
2014-10-20 16:18 ` Matt Fleming
2014-10-24 10:53 ` Peter Zijlstra
2014-10-28 23:22 ` Matt Fleming
2014-10-29 8:16 ` Peter Zijlstra
2014-10-29 12:48 ` Matt Fleming
2014-10-29 13:45 ` Peter Zijlstra
2014-10-29 16:32 ` Auld, Will
2014-10-29 17:28 ` Peter Zijlstra
2014-10-29 17:41 ` Vikas Shivappa
2014-10-29 18:22 ` Tejun Heo
2014-10-30 7:07 ` Peter Zijlstra
2014-10-30 7:14 ` Peter Zijlstra
2014-10-30 12:44 ` Tejun Heo
2014-10-30 13:19 ` Peter Zijlstra
2014-10-30 15:25 ` Tejun Heo
2014-10-30 12:43 ` Tejun Heo
2014-10-30 13:18 ` Peter Zijlstra
2014-10-30 17:03 ` Tejun Heo
2014-10-30 21:43 ` Peter Zijlstra
2014-10-30 22:22 ` Tejun Heo
2014-10-30 22:47 ` Peter Zijlstra
2014-11-06 16:27 ` Matt Fleming
2014-11-06 17:20 ` Vikas Shivappa
2014-10-31 13:07 ` Peter Zijlstra
2014-10-31 15:58 ` Tejun Heo
2014-11-04 13:13 ` Peter Zijlstra
2014-11-05 20:41 ` Tejun Heo
2014-10-30 14:14 ` Matt Fleming
[not found] ` <CAAAKZwvJOKsrj_yczDGaNLaNYo+_=HzsTLwDdcaTJqO2VMy8uA@mail.gmail.com>
2014-10-30 17:12 ` Tejun Heo
2014-10-30 22:35 ` Tim Hockin
2014-10-31 16:57 ` Tejun Heo
2014-10-30 23:18 ` Vikas Shivappa
2014-11-04 13:17 ` Peter Zijlstra
2014-11-06 17:03 ` Matt Fleming [this message]
2014-11-10 15:50 ` Peter Zijlstra
2014-10-29 17:26 ` Vikas Shivappa
2014-10-29 18:16 ` Peter Zijlstra
2014-11-03 23:29 ` Vikas Shivappa
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=20141106170323.GJ3592@console-pimps.org \
--to=matt@console-pimps.org \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=vikas.shivappa@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=will.auld@intel.com \
/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.