[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPhKKr8f6q=6m4T=-6PA8za-nMQMKy1HykAX-2NRaL9AZoPSjw@mail.gmail.com>
Date: Sat, 8 Sep 2012 09:36:29 -0400
From: Dhaval Giani <dhaval.giani@...il.com>
To: Paul Turner <pjt@...gle.com>
Cc: Tejun Heo <tj@...nel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Glauber Costa <glommer@...allels.com>,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
linux-mm@...ck.org, davej@...hat.com, ben@...adent.org.uk,
lennart@...ttering.net, kay.sievers@...y.org,
Frederic Weisbecker <fweisbec@...il.com>,
Balbir Singh <bsingharora@...il.com>,
Bharata B Rao <bharata@...ux.vnet.ibm.com>
Subject: Re: [RFC 0/5] forced comounts for cgroups.
On Thu, Sep 6, 2012 at 5:11 PM, Paul Turner <pjt@...gle.com> wrote:
> On Thu, Sep 6, 2012 at 1:46 PM, Tejun Heo <tj@...nel.org> wrote:
>> Hello,
>>
>> cc'ing Dhaval and Frederic. They were interested in the subject
>> before and Dhaval was pretty vocal about cpuacct having a separate
>> hierarchy (or at least granularity).
>
> Really? Time just has _not_ borne out this use-case. I'll let Dhaval
> make a case for this but he should expect violent objection.
>
I am not objecting directly! I am aware of a few users who are (or at
least were) using cpu and cpuacct separately because they want to be
able to account without control. Having said that, there are tons of
flaws in the current approach, because the accounting without control
is just plain wrong. I have copied a few other folks who might be able
to shed light on those users and if we should still consider them.
[And the lesser number of controllers, the better it is!]
Thanks!
Dhaval
--
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