Re: [RFC] cgroup TODOs

From: Michal Hocko
Date: Fri Sep 14 2012 - 11:03:08 EST

On Thu 13-09-12 13:58:27, Tejun Heo wrote:
> 2. memcg's __DEPRECATED_clear_css_refs
> This is a remnant of another weird design decision of requiring
> synchronous draining of refcnts on cgroup removal and allowing
> subsystems to veto cgroup removal - what's the userspace supposed to
> do afterwards? Note that this also hinders co-mounting different
> controllers.
> The behavior could be useful for development and debugging but it
> unnecessarily interlocks userland visible behavior with in-kernel
> implementation details. To me, it seems outright wrong (either
> implement proper severing semantics in the controller or do full
> refcnting) and disallows, for example, lazy drain of caching refs.
> Also, it complicates the removal path with try / commit / revert
> logic which has never been fully correct since the beginning.
> Currently, the only left user is memcg.
> Solution:
> * Update memcg->pre_destroy() such that it never fails.
> * Drop __DEPRECATED_clear_css_refs and all related logic.
> Convert pre_destroy() to return void.
> Who:
> KAMEZAWA, Michal, PLEASE. I will make __DEPRECATED_clear_css_refs
> trigger WARN sooner or later. Let's please get this settled.

I think we are almost there. One big step was that we no longer charge
to the parent and only move statistics but there are still some corner
cases when we race with LRU handling.

> * memcg can be fully hierarchical but we need to phase out the flat
> hierarchy support. Unfortunately, this involves flipping the
> behavior for the existing users. Upstream will try to nudge users
> with warning messages. Most burden would be on the distros and at
> least SUSE seems to be on board with it. Needs coordination with
> other distros.

I am currently planning to add a warning to most of the currenly
maintained distributions to have as big coverage as possible. No default
switch for obvious reasons but hopefuly we will get some feedback at

Thanks Tejun for doing this. We needed it for a long time.
Michal Hocko
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at