[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120921214002.GA7694@google.com>
Date: Fri, 21 Sep 2012 14:40:02 -0700
From: Tejun Heo <tj@...nel.org>
To: containers@...ts.linux-foundation.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Li Zefan <lizefan@...wei.com>, Michal Hocko <mhocko@...e.cz>,
Glauber Costa <glommer@...allels.com>,
Peter Zijlstra <peterz@...radead.org>,
Paul Turner <pjt@...gle.com>,
Johannes Weiner <hannes@...xchg.org>,
Thomas Graf <tgraf@...g.ch>,
"Serge E. Hallyn" <serue@...ibm.com>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Neil Horman <nhorman@...driver.com>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: Re: [RFC] cgroup TODOs
On Thu, Sep 13, 2012 at 01:58:27PM -0700, Tejun Heo wrote:
> 7. Misc issues
>
> * Sort & unique when listing tasks. Even the documentation says it
> doesn't happen but we have a good hunk of code doing it in
> cgroup.c. I'm gonna rip it out at some point. Again, if you
> don't like it, scream.
>
> * At the PLC, pjt told me that assinging threads of a cgroup to
> different cgroups is useful for some use cases but if we're to
> have a unified hierarchy, I don't think we can continue to do
> that. Paul, can you please elaborate the use case?
>
> * Vivek brought up the issue of distributing resources to tasks and
> groups in the same cgroup. I don't know. Need to think more
> about it.
* Update docs.
* Clean up cftype->read/write*() mess.
* Use sane fs event mechanism.
* Drop userland helper based empty notification. Argh...
--
tejun
--
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