Re: [PATCH 12/12] memcg: don't need to free memcg via RCU or workqueue

(2013/04/08 15:36), Li Zefan wrote: > Now memcg has the same life cycle with its corresponding cgroup, and > a cgroup is freed via RCU and then mem_cgroup_css_free() is called > in a work function, so we can simply call __mem_cgroup_free() in > mem_cgroup_css_free(). > > This actually reverts 5992

Re: [PATCH 12/12] memcg: don't need to free memcg via RCU or workqueue

On Mon 08-04-13 14:36:32, Li Zefan wrote: > Now memcg has the same life cycle with its corresponding cgroup, and > a cgroup is freed via RCU and then mem_cgroup_css_free() is called > in a work function, so we can simply call __mem_cgroup_free() in > mem_cgroup_css_free(). > > This actually revert

[PATCH 12/12] memcg: don't need to free memcg via RCU or workqueue

Now memcg has the same life cycle with its corresponding cgroup, and a cgroup is freed via RCU and then mem_cgroup_css_free() is called in a work function, so we can simply call __mem_cgroup_free() in mem_cgroup_css_free(). This actually reverts 59927fb984de1703c67bc640c3e522d8b5276c73 ("memcg: fr