From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 19 Nov 2007 15:35:49 +0900 From: KAMEZAWA Hiroyuki Subject: Re: [RFC][PATCH] memory controller per zone patches take 2 [9/10] per-zone-lru for memory cgroup Message-Id: <20071119153549.d6f6f1de.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <47412B5B.80409@linux.vnet.ibm.com> References: <20071116191107.46dd523a.kamezawa.hiroyu@jp.fujitsu.com> <20071116192642.8c7f07c9.kamezawa.hiroyu@jp.fujitsu.com> <473F2A1A.8000703@linux.vnet.ibm.com> <20071119104826.e4ba02ca.kamezawa.hiroyu@jp.fujitsu.com> <47412B5B.80409@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: balbir@linux.vnet.ibm.com Cc: "containers@lists.osdl.org" , "linux-mm@kvack.org" , "yamamoto@valinux.co.jp" List-ID: On Mon, 19 Nov 2007 11:51:15 +0530 Balbir Singh wrote: > > = > > /cgroup/group_A/group_A_1 > > . /group_A_2 > > /group_A_3 > > (LRU(s) will be used for maintaining parent/child groups.) > > > > The LRU's will be shared, my vision is > > LRU > ^ ^ > | | > Mem-----+ +----Mem > > > That two or more mem_cgroup's can refer to the same LRU list and have > their own resource counters. This setup will be used in the case > of a hierarchy, so that a child can share memory with its parent > and have it's own limit. > > The mem_cgroup will basically then only contain a reference > to the LRU list. > Hmm, interesting. Then, group_A_1's usage + group_A_2's usage + group_A_3's usgae < group_A's limit. group_A_1, group_A_2, group_A_3 has its own limit. In plan. I wonder if we want rich control functions, we need "share" or "priority" among childs. (but maybe this will be complicated one.) Thank you for explanation. 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/ . Don't email: email@kvack.org