From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Vikas Shivappa <vikas.shivappa@intel.com>,
"Auld, Will" <will.auld@intel.com>,
Matt Fleming <matt@console-pimps.org>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Fleming, Matt" <matt.fleming@intel.com>
Subject: Re: Cache Allocation Technology Design
Date: Thu, 30 Oct 2014 08:14:24 +0100 [thread overview]
Message-ID: <20141030071424.GE10476@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20141030070725.GG3337@twins.programming.kicks-ass.net>
On Thu, Oct 30, 2014 at 08:07:25AM +0100, Peter Zijlstra wrote:
> > and always allow execution of member tasks.
This too btw is not strictly speaking possible for all controllers. Most
all sched controllers live by the grace of forcing tasks not to run at
times (eg. the bandwidth controls), falsifying the 'always'.
next prev parent reply other threads:[~2014-10-30 7:14 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 [this message]
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
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=20141030071424.GE10476@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox