[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1410291036070.26215@vshiva-Udesk>
Date: Wed, 29 Oct 2014 10:41:47 -0700 (PDT)
From: Vikas Shivappa <vikas.shivappa@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
cc: "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>,
Tejun Heo <tj@...nel.org>,
"Shivappa, Vikas" <vikas.shivappa@...el.com>
Subject: Re: Cache Allocation Technology Design
On Wed, 29 Oct 2014, Peter Zijlstra wrote:
> 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.
>
Was wondering if it is a requirement of the 'full hierarchy' for the
child to inherit the cbm of parent ? .
Alternately we can allocate the CLOSid when a cgroup
is created and have an empty cbm - but dont let the tasks to be added
unless the user assigns a cbm. Cpuset does something similar where
its necessary to set the cpu mask(empty by default) of a cgroup before adding
tasks.
--
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/
Powered by blists - more mailing lists