From mboxrd@z Thu Jan 1 00:00:00 1970 From: KAMEZAWA Hiroyuki Subject: [PATCH v3][0/6] memcg: prevent -ENOMEM in pre_destroy() Date: Fri, 11 May 2012 18:41:36 +0900 Message-ID: <4FACDED0.3020400@jp.fujitsu.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org" Cc: "cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Michal Hocko , Johannes Weiner , Frederic Weisbecker , Han Ying , Glauber Costa , Tejun Heo , "Aneesh Kumar K.V" , Andrew Morton , Hiroyuki Kamezawa , Linux Kernel 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). Regards, -Kame From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx110.postini.com [74.125.245.110]) by kanga.kvack.org (Postfix) with SMTP id 176338D0001 for ; Fri, 11 May 2012 05:43:36 -0400 (EDT) Received: from m4.gw.fujitsu.co.jp (unknown [10.0.50.74]) by fgwmail5.fujitsu.co.jp (Postfix) with ESMTP id 34C563EE0C2 for ; Fri, 11 May 2012 18:43:34 +0900 (JST) Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id F082945DE6B for ; Fri, 11 May 2012 18:43:33 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (s4.gw.fujitsu.co.jp [10.0.50.94]) by m4.gw.fujitsu.co.jp (Postfix) with ESMTP id D803A45DE68 for ; Fri, 11 May 2012 18:43:33 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id C906E1DB8042 for ; Fri, 11 May 2012 18:43:33 +0900 (JST) Received: from m1000.s.css.fujitsu.com (m1000.s.css.fujitsu.com [10.240.81.136]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 7687B1DB803B for ; Fri, 11 May 2012 18:43:33 +0900 (JST) Message-ID: <4FACDED0.3020400@jp.fujitsu.com> Date: Fri, 11 May 2012 18:41:36 +0900 From: KAMEZAWA Hiroyuki MIME-Version: 1.0 Subject: [PATCH v3][0/6] memcg: prevent -ENOMEM in pre_destroy() Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: "linux-mm@kvack.org" Cc: "cgroups@vger.kernel.org" , Michal Hocko , Johannes Weiner , Frederic Weisbecker , Han Ying , Glauber Costa , Tejun Heo , "Aneesh Kumar K.V" , Andrew Morton , Hiroyuki Kamezawa , Linux Kernel 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). Regards, -Kame -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758897Ab2EKJnh (ORCPT ); Fri, 11 May 2012 05:43:37 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:40643 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755302Ab2EKJnf (ORCPT ); Fri, 11 May 2012 05:43:35 -0400 X-SecurityPolicyCheck: OK by SHieldMailChecker v1.7.4 Message-ID: <4FACDED0.3020400@jp.fujitsu.com> Date: Fri, 11 May 2012 18:41:36 +0900 From: KAMEZAWA Hiroyuki User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: "linux-mm@kvack.org" CC: "cgroups@vger.kernel.org" , Michal Hocko , Johannes Weiner , Frederic Weisbecker , Han Ying , Glauber Costa , Tejun Heo , "Aneesh Kumar K.V" , Andrew Morton , Hiroyuki Kamezawa , Linux Kernel Subject: [PATCH v3][0/6] memcg: prevent -ENOMEM in pre_destroy() Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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). Regards, -Kame