Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750763AbWIOLPt (ORCPT ); Fri, 15 Sep 2006 07:15:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750798AbWIOLPs (ORCPT ); Fri, 15 Sep 2006 07:15:48 -0400 Received: from mailhub.sw.ru ([195.214.233.200]:18217 "EHLO relay.sw.ru") by vger.kernel.org with ESMTP id S1750763AbWIOLPs (ORCPT ); Fri, 15 Sep 2006 07:15:48 -0400 Message-ID: <450A8B61.7040905@openvz.org> Date: Fri, 15 Sep 2006 15:15:45 +0400 From: Pavel Emelianov User-Agent: Thunderbird 1.5 (X11/20060317) MIME-Version: 1.0 To: sekharan@us.ibm.com, balbir@in.ibm.com, Srivatsa CC: Kirill Korotaev , Rik van Riel , CKRM-Tech , Dave Hansen , Linux Kernel Mailing List , Andi Kleen , Christoph Hellwig , Andrey Savochkin , devel@openvz.org, Matt Helsley , Hugh Dickins , Alexey Dobriyan , Oleg Nesterov , Alan Cox Subject: Re: [ckrm-tech] [PATCH] BC: resource beancounters (v4) (added user memory) References: <44FD918A.7050501@sw.ru> <44FDAB81.5050608@in.ibm.com> <44FEC7E4.7030708@sw.ru> <44FF1EE4.3060005@in.ibm.com> <1157580371.31893.36.camel@linuxchandra> <45011CAC.2040502@openvz.org> <1157730221.26324.52.camel@localhost.localdomain> <4501B5F0.9050802@in.ibm.com> <450508BB.7020609@openvz.org> <4505161E.1040401@in.ibm.com> <45051AC7.2000607@openvz.org> <1158000590.6029.33.camel@linuxchandra> <45069072.4010007@openvz.org> <1158105488.4800.23.camel@linuxchandra> <4507BC11.6080203@openvz.org> <1158186664.18927.17.camel@linuxchandra> <45090A6E.1040206@openvz.org> <1158277364.6357.33.camel@linuxchandra> <450A5325.6090803@openvz.org> <450A6A7A.8010102@sw.ru> In-Reply-To: <450A6A7A.8010102@sw.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1346 Lines: 31 Kirill Korotaev wrote: [snip] >> I have a C program that computes limits to obtain desired guarantees >> in a single 'for (i = 0; i < n; n++)' loop for any given set of guarantees. >> With all error handling, beautifull output, nice formatting etc it weights >> only 60 lines. Look at http://wiki.openvz.org/Containers/Guarantees_for_resources I've described there how a guarantee can be get with limiting in details. [snip] >> I do not 'do not like guarantee'. I'm just sure that there are two ways >> for providing guarantee (for unreclaimable resorces): >> 1. reserving resource for group in advance >> 2. limit resource for others >> Reserving is worse as it is essentially limiting (you cut off 100Mb from >> 1Gb RAM thus limiting the other groups by 900Mb RAM), but this limiting >> is too strict - you _have_ to reserve less than RAM size. Limiting in >> run-time is more flexible (you may create an overcommited BC if you >> want to) and leads to the same result - guarantee. > I think this deserves putting on Wiki. > It is very good clear point. This is also on the page I gave link at. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/