Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763074Ab3DCJS4 (ORCPT ); Wed, 3 Apr 2013 05:18:56 -0400 Received: from mx2.parallels.com ([199.115.105.18]:40442 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763043Ab3DCJSy (ORCPT ); Wed, 3 Apr 2013 05:18:54 -0400 Message-ID: <515BF41D.9080300@parallels.com> Date: Wed, 3 Apr 2013 13:19:25 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: Li Zefan CC: , LKML , Cgroups , Tejun Heo , Michal Hocko , KAMEZAWA Hiroyuki , Johannes Weiner Subject: Re: [RFC][PATCH 0/7] memcg: make memcg's life cycle the same as cgroup References: <515BF233.6070308@huawei.com> In-Reply-To: <515BF233.6070308@huawei.com> Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 994 Lines: 22 On 04/03/2013 01:11 PM, Li Zefan wrote: > The historical reason that memcg didn't use css_get in some cases, is that > cgroup couldn't be removed if there're still css refs. The situation has > changed so that rmdir a cgroup will succeed regardless css refs, but won't > be freed until css refs goes down to 0. > > This is an early post, and it's NOT TESTED. I just want to see if the changes > are fine in general. Well, from my PoV, this will in general greatly simplify memcg lifecycle management. Indeed, I can remember no other reason for those complications other than the problem with removing directories. If cgroup no longer have this limitation, I would much rather see your approach in. I will look into the patches individually soon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/