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: <20141029172845.GP12706@worktop.programming.kicks-ass.net>
Date:	Wed, 29 Oct 2014 18:28:45 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	"Auld, Will" <will.auld@...el.com>
Cc:	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>,
	Tejun Heo <tj@...nel.org>,
	"Shivappa, Vikas" <vikas.shivappa@...el.com>
Subject: Re: Cache Allocation Technology Design

On Wed, Oct 29, 2014 at 04:32:04PM +0000, Auld, Will wrote:
> I maybe repeating what Peter has just said but for elements in the
> hierarchy where the mask is the same as its parents mask there is no
> need for a separate CLOS even in the case where there are tasks in the
> group. So we can inherit the CLOS of the parent until which time both
> the mask is different than the parent and there are tasks in the
> group. 

I did not state that explicitly, but I did think about that. We could
still wait to allocate a CLOS until at least one such group acquires a
task.
--
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/