Hey, Lennart. On Mon, Mar 12, 2012 at 11:31:14PM +0100, Lennart Poettering wrote: > > On Mon, Mar 12, 2012 at 11:22:18PM +0100, Peter Zijlstra wrote: > > > On Mon, 2012-03-12 at 15:10 -0700, Tejun Heo wrote: > > > > > > > > * How to map controllers which aren't aware of full hierarchy is still > > > > an open question but I'm still standing by one active node on any > > > > root-to-leaf path w/ root group serving as the special rest group. > > > > > > What does this mean? > > > > Let's say we have a tree like the following. > > > > root > > / | \ > > G1 G2 G3 > > / \ > > G31 G32 > > > > So, for cgroups which don't support full hierarchy, it'll be viewed as > > either, > > > > root > > / | \ > > G1 G2 G3 > > > > or > > > > root > > / | | \ > > G1 G2 G31 G32 > > > > With root being treated specially, probably as just being a equal > > group as other groups, I'm not fully determined about that yet. > > Note that at least systemd places all services by default beneath a > single "super" group (/system/), hence the first suggestion would make > little sense for us. The second suggestion would be fine however. Ooh, both will be available to choose from. I was trying to explain that there can be configuration only at one layer for any task so that it can be mapped to flat hierarchy. Where to apply the config will be selected by the user (or system tool). Thanks. -- tejun -- 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
