On 04/11/2012 10:07 PM, Johannes Weiner wrote:
You could also twist this around and argue the same for cpu usage and
make it part of the cpu cgroup, but it doesn't really fit in either
subsystem, IMO.
I myself really prefer this in the cpu controller.
Besides the bytes vs objects things, Whenever you create a process, at
some point it will end up in the runqueues to be scheduled. It is a
natural point of accounting.
Either that, or making it a core feature of cgroups, like limiting the
number of processes in the tasks file (just have to find a natural way
to make it hierarchical). It will make more and more sense as people
seem to be favoring single hierarchies these days. (granted, not a
settled discussion, so your views may vary)
--
To unsubscribe from this list: send the line "unsubscribe cgroups" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
