Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030317AbWILSDY (ORCPT ); Tue, 12 Sep 2006 14:03:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030322AbWILSDX (ORCPT ); Tue, 12 Sep 2006 14:03:23 -0400 Received: from smtp-out.google.com ([216.239.45.12]:64490 "EHLO smtp-out.google.com") by vger.kernel.org with ESMTP id S1030317AbWILSDW (ORCPT ); Tue, 12 Sep 2006 14:03:22 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:subject:from:reply-to:to:cc:in-reply-to:references: content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=FMgxRV7scyFhG2ojnZR0TH4HQeMI2ulUaUPOlOaqMeKZrIzSdXx6IPiFqAcBl2Qy3 laay6VJgjqJnEFJivIGXg== Subject: Re: [ckrm-tech] [PATCH] BC: resource beancounters (v4) (added user memory) From: Rohit Seth Reply-To: rohitseth@google.com To: vatsa@in.ibm.com Cc: sekharan@us.ibm.com, Rik van Riel , Alan Cox , CKRM-Tech , balbir@in.ibm.com, Dave Hansen , Linux Kernel Mailing List , Andi Kleen , Christoph Hellwig , Andrey Savochkin , Matt Helsley , Hugh Dickins , Alexey Dobriyan , Kirill Korotaev , Oleg Nesterov , devel@openvz.org, Pavel Emelianov In-Reply-To: <20060912174058.GA2932@in.ibm.com> References: <44FEC7E4.7030708@sw.ru> <44FF1EE4.3060005@in.ibm.com> <1157580371.31893.36.camel@linuxchandra> <45011CAC.2040502@openvz.org> <1157743424.19884.65.camel@linuxchandra> <1157751834.1214.112.camel@galaxy.corp.google.com> <1157999107.6029.7.camel@linuxchandra> <1158001831.12947.16.camel@galaxy.corp.google.com> <20060912104410.GA28444@in.ibm.com> <1158081752.20211.12.camel@galaxy.corp.google.com> <20060912174058.GA2932@in.ibm.com> Content-Type: text/plain Organization: Google Inc Date: Tue, 12 Sep 2006 11:02:18 -0700 Message-Id: <1158084138.20211.26.camel@galaxy.corp.google.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2070 Lines: 47 On Tue, 2006-09-12 at 23:10 +0530, Srivatsa Vaddagiri wrote: > On Tue, Sep 12, 2006 at 10:22:32AM -0700, Rohit Seth wrote: > > On Tue, 2006-09-12 at 16:14 +0530, Srivatsa Vaddagiri wrote: > > > On Mon, Sep 11, 2006 at 12:10:31PM -0700, Rohit Seth wrote: > > > > It seems that a single notion of limit should suffice, and that limit > > > > should more be treated as something beyond which that resource > > > > consumption in the container will be throttled/not_allowed. > > > > > > The big question is : are containers/RG allowed to use *upto* their > > > limit always? In other words, will you typically setup limits such that > > > sum of all limits = max resource capacity? > > > > > > > If a user is really interested in ensuring that all scheduled jobs (or > > containers) get what they have asked for (guarantees) then making the > > sum of all container limits equal to total system limit is the right > > thing to do. > > > > > If it is setup like that, then what you are considering as limit is > > > actually guar no? > > > > > Right. And if we do it like this then it is up to sysadmin to configure > > the thing right without adding additional logic in kernel. > > Perhaps calling it as "limit" in confusing then (otoh it may go down well > with Linus!). It is similar to what ulimit generally implies. It will definitely help getting container code in mainline if we can minimize the changes in mainline but still providing some meaningful functionality. CKRM is excellent piece of code but I think its complexity is what making it sit out side the mainline for such a long period of time. > I perhaps agree we need to go with one for now (in the > interest of making some progress), but we probably will come back to > this at a later point. Indeed if there are still some requirements. -rohit - 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/