On 01/21/2013 08:07 PM, Michal Hocko wrote: >> > And the reason why kmemcg holds the set_limit mutex >> > is just to protect from itself, then there is no *need* to hold any >> > extra lock (and we'll never be able to stop holding the creation lock, >> > whatever it is). So my main point here is not memcg_mutex vs >> > set_limit_mutex, but rather, memcg_mutex is needed anyway, and once it >> > is taken, the set_limit_mutex *can* be held, but doesn't need to. > So you can update kmem specific usage of set_limit_mutex. Meaning ? -- 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
