From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <47CFB065.3080200@openvz.org> Date: Thu, 06 Mar 2008 11:50:45 +0300 From: Pavel Emelyanov MIME-Version: 1.0 Subject: Re: [Devel] Re: [RFC/PATCH] cgroup swap subsystem References: <47CE36A9.3060204@mxp.nes.nec.co.jp> <47CE5AE2.2050303@openvz.org> <47CEAAB4.8070208@openvz.org> <20080306093324.77c6d7f4.kamezawa.hiroyu@jp.fujitsu.com> <47CFA941.4070507@openvz.org> <20080306173347.f6c5c84c.kamezawa.hiroyu@jp.fujitsu.com> <47CFAD69.6000909@openvz.org> <6599ad830803060048sb39735an765a62e6b928657e@mail.gmail.com> In-Reply-To: <6599ad830803060048sb39735an765a62e6b928657e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Paul Menage Cc: KAMEZAWA Hiroyuki , balbir@linux.vnet.ibm.com, containers@lists.osdl.org, Hugh Dickins , linux-mm@kvack.org List-ID: Paul Menage wrote: > On Thu, Mar 6, 2008 at 12:38 AM, Pavel Emelyanov wrote: >> > Hierarchical res_counter makes sense. >> > Making it in simple/reasonable style will be our challenge. >> >> I have this in my TODO list. Since this is not so urgent, then if you >> don't mind I can prepare the patches next week - after I set the git >> tree up. This change doesn't seem that big. >> > > The change that you're referring to is allowing a cgroup to have a > total memory limit for itself and all its children, and then giving > that cgroup's children separate memory limits within that overall > limit? Yup. Isn't this reasonable? Without this, if I'm a task in a 1GB limited cgroup, I can create a new one, set 2GB limit and spawn a kid into it (or move there myself) and be happy with 2GB of memory... With the proposed change, even if I set a 2GB for a subgroup it will not pass _my_ (1GB) limit. > Paul > -- 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