From: Kamezawa Hiroyuki Subject: Re: [PATCH 12/12] memcg: don't need to free memcg via RCU or workqueue Date: Tue, 09 Apr 2013 11:57:49 +0900 Message-ID: <516383AD.9010305@jp.fujitsu.com> References: <5162648B.9070802@huawei.com> <51626570.8000400@huawei.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51626570.8000400-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Li Zefan Cc: Andrew Morton , Tejun Heo , Glauber Costa , Johannes Weiner , LKML , Cgroups , linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, Hugh Dickins (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 59927fb984de1703c67bc640c3e522d8b5276c73 > ("memcg: free mem_cgroup by RCU to fix oops"). > > Cc: Hugh Dickins > Signed-off-by: Li Zefan Very nice. Acked-by: KAMEZAWA Hiroyuki