On Mon 03-12-12 15:44:20, Andrew Morton wrote: > On Mon, 3 Dec 2012 17:24:08 +0400 > Glauber Costa <glommer@xxxxxxxxxxxxx> wrote: > > > If memcg is tracking anything other than plain user memory (swap, tcp > > buf mem, or slab memory), it is possible - and normal - that a reference > > will be held by the group after it is dead. Still, for developers, it > > would be extremely useful to be able to query about those states during > > debugging. > > > > This patch provides a debugging facility in the root memcg, so we can > > inspect which memcgs still have pending objects, and what is the cause > > of this state. > > As this is a developer-only thing, I suggest that we should avoid > burdening mainline with it. How about we maintain this in -mm (and > hence in -next and mhocko's memcg tree) until we no longer see a need > for it? Yes, that makes sense. It can produce some conflicts but they should be trivial to resolve. -- Michal Hocko SUSE Labs -- 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
