Re: [RFC PATCH-cgroup 1/6] cgroup: Relax the no internal process constraint

From: Tejun Heo
Date: Wed Jun 21 2017 - 17:39:12 EST


On Wed, Jun 21, 2017 at 05:37:00PM -0400, Waiman Long wrote:
> > What happens when we add domain handling to CPU so that it is both a
> > domain and resource controller? Even if that somehow can be resolved,
> > wouldn't that come with a rather surprising userland behavior changes?
> > Also, I'm not sure what we're achieving by doing this. It doesn't
> > really relax the restriction. It just turns it off implicitly when
> > certain conditions are met, which doesn't really allow any real
> > capabilities and at least to me the behaviors feel more subtle and
> > complicated than before.
> I think CPU isn't a good example for that.

Can you please elaborate?

> Another alternative is to treat no internal process as a controller
> attribute. Then we don't need to worry about this intricate question and
> let the controllers decide if they will allow internal processes.

Isn't that what "threaded" is?