linux-kernel - Re: Cache Allocation Technology Design

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141030131904.GJ3337@twins.programming.kicks-ass.net>
Date:	Thu, 30 Oct 2014 14:19:04 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	Vikas Shivappa <vikas.shivappa@...el.com>,
	"Auld, Will" <will.auld@...el.com>,
	Matt Fleming <matt@...sole-pimps.org>,
	Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Fleming, Matt" <matt.fleming@...el.com>
Subject: Re: Cache Allocation Technology Design

On Thu, Oct 30, 2014 at 08:44:40AM -0400, Tejun Heo wrote:
> On Thu, Oct 30, 2014 at 08:14:24AM +0100, Peter Zijlstra wrote:
> > 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'.
> 
> Oh sure, the a task just has to run in a foreseeable future, or
> rather, a task must not be blocked indefinitely requiring userland
> intervention to become executable again.

Like the freezer cgroup you mean? ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/