[PATCH 2/8] cgroup: kill CSS_REMOVED
tj at kernel.org
Wed Oct 31 17:10:44 UTC 2012
On Wed, Oct 31, 2012 at 10:06 AM, Glauber Costa <glommer at parallels.com> wrote:
> This is not the topic of this thread, but since you brought it:
> If you take a look at the description patch in the patch I sent, the
> problem I outlined is that at create time, we don't know anything about
> which will the css_id be - and I would like to avoid creating yet
> another index.
> Is there any way you would suggest of handling this ? Any chance of us
> allocating the css_id earlier then?
I only glanced the patch description but the problem I'm trying to
solve is locking - currently we don't have a place where a controller
can tell a cgroup is becoming online; thus it has nothing to
synchronized against and tell that a cgroup is alive or not. As for
css_id allocation, maybe you can deal with that in ->post_create() or
maybe we can allocate css_id earlier (but where would it be stored?).
I'll look into it.
More information about the Containers