lkml.org 
[lkml]   [2012]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFD] cgroup: about multiple hierarchies
From
Date
On Mon, 2012-03-12 at 15:28 -0700, Tejun Heo wrote:
> Hey,
>
> 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.

I'm assuming that G31/G32's tasks end up in G3 in the first case, but
where do the tasks in G3 go to in the second case?

Also, why allow non-hierarchical controllers to begin with? I would very
much argue for mandating that all controllers work the same wrt
hierarchy and if that means ditching hierarchy support we should do that
and modify cgroupfs to not allow creation of directories deeper than 1.

But allowing controllers that implement hierarchy proper and controllers
that do not and then force them in the same mount point, that just
doesn't make any friggin sense what so ever.


\
 
 \ /
  Last update: 2012-03-12 23:37    [from the cache]
©2003-2011 Jasper Spaans