From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from d28relay02.in.ibm.com (d28relay02.in.ibm.com [9.184.220.59]) by e28smtp03.in.ibm.com (8.13.1/8.13.1) with ESMTP id mAG8Aa6p030192 for ; Sun, 16 Nov 2008 13:40:36 +0530 Received: from d28av03.in.ibm.com (d28av03.in.ibm.com [9.184.220.65]) by d28relay02.in.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mAG8AEEl1581118 for ; Sun, 16 Nov 2008 13:40:14 +0530 Received: from d28av03.in.ibm.com (loopback [127.0.0.1]) by d28av03.in.ibm.com (8.13.1/8.13.3) with ESMTP id mAG8ACeR025781 for ; Sun, 16 Nov 2008 13:40:13 +0530 From: Balbir Singh Date: Sun, 16 Nov 2008 13:40:34 +0530 Message-Id: <20081116081034.25166.7586.sendpatchset@balbir-laptop> Subject: [mm][PATCH 0/4] Memory cgroup hierarchy introduction (v4) Sender: owner-linux-mm@kvack.org Return-Path: To: linux-mm@kvack.org Cc: YAMAMOTO Takashi , Paul Menage , lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org, Nick Piggin , David Rientjes , Pavel Emelianov , Dhaval Giani , Balbir Singh , Andrew Morton , KAMEZAWA Hiroyuki List-ID: This patch follows several iterations of the memory controller hierarchy patches. The hardwall approach by Kamezawa-San[1]. Version 1 of this patchset at [2]. The current approach is based on [2] and has the following properties 1. Hierarchies are very natural in a filesystem like the cgroup filesystem. A multi-tree hierarchy has been supported for a long time in filesystems. When the feature is turned on, we honor hierarchies such that the root accounts for resource usage of all children and limits can be set at any point in the hierarchy. Any memory cgroup is limited by limits along the hierarchy. The total usage of all children of a node cannot exceed the limit of the node. 2. The hierarchy feature is selectable and off by default 3. Hierarchies are expensive and the trade off is depth versus performance. Hierarchies can also be completely turned off. The patches are against 2.6.28-rc2-mm1 and were tested in a KVM instance with SMP and swap turned on. Signed-off-by: Balbir Singh v4..v3 ====== Move to iteration instead of recursion in hierarchical reclaim. Thanks go out to Kamezawa for pushing this Port the patches to 2.6.28-rc4 (mmotm 15th November) v3..v2 ====== 1. Hierarchy selection logic, now allows use_hierarchy changes only if parent's use_hierarchy is set to 0 and there are no children 2. last_scanned_child is protected by cgroup_lock() 3. cgroup_lock() is released before lru_add_drain_all() in mem_cgroup_force_empty() v2..v1 ====== 1. The hierarchy is now selectable per-subtree 2. The features file has been renamed to use_hierarchy 3. Reclaim now holds cgroup lock and the reclaim does recursive walk and reclaim Acknowledgements ---------------- Thanks for the feedback from Li Zefan, Kamezawa Hiroyuki, Paul Menage and others. Series ------ memcg-hierarchy-documentation.patch resource-counters-hierarchy-support.patch memcg-hierarchical-reclaim.patch memcg-add-hierarchy-selector.patch Reviews? Comments? References 1. http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-06/msg05417.html 2. http://kerneltrap.org/mailarchive/linux-kernel/2008/4/19/1513644/thread -- Balbir -- 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/ . Don't email: email@kvack.org