From: Tejun Heo Subject: Re: [PATCH v3][0/6] memcg: prevent -ENOMEM in pre_destroy() Date: Thu, 21 Jun 2012 13:20:43 -0700 Message-ID: <20120621202043.GD4642@google.com> References: <4FACDED0.3020400@jp.fujitsu.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=si6AcncGc9JLOlYmBVfnZ9PXSOXs6yjUMjnt1K8uXsI=; b=J22JPGQDtRFpy3+Vj4vu16ATm2/09ATQoRlb4DU3asAwVUlT6FvORNpor45YzmqgY1 SE84x6XjzESfJEMIQbydPKNIEQVmg5h3JBPEWcqJGGMf/u/suJC8NVbgc5eo/daoneHu 7NmGgzzOnjfLayL7ZekBDEjMtqsBEqg0p+dmezkjgGoQ9+JHkdlN6RLnOOTaJPmwjpWZ 4rRMrKUMxCxmICsobh2JFUk8zB92k7NKs6sNHxJ1HJw7GHGFYlHeMc1zf8SpqAh0bRAJ v9cGvzKeLXhX+daurbFlLuDU5iSN5a0sW8zIQ5XMMNQlp7nSctt7XvG2992NRJtqxLAW tedQ== Content-Disposition: inline In-Reply-To: <4FACDED0.3020400-+CUm20s59erQFUHtdCDX3A@public.gmane.org> Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: KAMEZAWA Hiroyuki Cc: "linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org" , "cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Michal Hocko , Johannes Weiner , Frederic Weisbecker , Han Ying , Glauber Costa , "Aneesh Kumar K.V" , Andrew Morton , Hiroyuki Kamezawa , Linux Kernel On Fri, May 11, 2012 at 06:41:36PM +0900, KAMEZAWA Hiroyuki wrote: > Hi, here is v3 based on memcg-devel tree. > git://github.com/mstsxfx/memcg-devel.git > > This patch series is for avoiding -ENOMEM at calling pre_destroy() > which is called at rmdir(). After this patch, charges will be moved > to root (if use_hierarchy==0) or parent (if use_hierarchy==1), and > we'll not see -ENOMEM in rmdir() of cgroup. > > v2 included some other patches than ones for handling -ENOMEM problem, > but I divided it. I'd like to post others in different series, later. > No logical changes in general, maybe v3 is cleaner than v2. > > 0001 ....fix error code in memcg-hugetlb > 0002 ....add res_counter_uncharge_until > 0003 ....use res_counter_uncharge_until in memcg > 0004 ....move charges to root is use_hierarchy==0 > 0005 ....cleanup for mem_cgroup_move_account() > 0006 ....remove warning of res_counter_uncharge_nofail (from Costa's slub accounting series). KAME, how is this progressing? Is it stuck on anything? Thank you very much. -- tejun