Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751577AbWHYWwz (ORCPT ); Fri, 25 Aug 2006 18:52:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751574AbWHYWwy (ORCPT ); Fri, 25 Aug 2006 18:52:54 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:59817 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1751493AbWHYWwy (ORCPT ); Fri, 25 Aug 2006 18:52:54 -0400 Subject: Re: [ckrm-tech] [RFC][PATCH] UBC: user resource beancounters From: Alan Cox To: sekharan@us.ibm.com Cc: Rik van Riel , ckrm-tech@lists.sourceforge.net, Linux Kernel Mailing List , Andi Kleen , Christoph Hellwig , Andrey Savochkin , rohitseth@google.com, hugh@veritas.com, Ingo Molnar , Kirill Korotaev , devel@openvz.org, Pavel Emelianov In-Reply-To: <1156544604.1196.62.camel@linuxchandra> References: <44E33893.6020700@sw.ru> <1155929992.26155.60.camel@linuxchandra> <44E9B3F5.3010000@sw.ru> <1156196721.6479.67.camel@linuxchandra> <1156211128.11127.37.camel@galaxy.corp.google.com> <1156272902.6479.110.camel@linuxchandra> <1156383881.8324.51.camel@galaxy.corp.google.com> <1156385072.7154.59.camel@linuxchandra> <1156440461.14648.26.camel@galaxy.corp.google.com> <1156463572.19702.46.camel@linuxchandra> <44EEDB23.9050006@sw.ru> <1156531644.1196.26.camel@linuxchandra> <1156539168.3007.264.camel@localhost.localdomain> <1156544604.1196.62.camel@linuxchandra> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Sat, 26 Aug 2006 00:12:52 +0100 Message-Id: <1156547572.3007.279.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1345 Lines: 29 Ar Gwe, 2006-08-25 am 15:23 -0700, ysgrifennodd Chandra Seetharaman: > > Bean counters can exist with no tasks, and the CKRM people have been > > corrected repeatedly on this point. > > Hmm... from what I understand from the code, when the last resource in > the beancounter is dropped, the beancounter is destroyed. Which to me > means that when there are no tasks in a beancounter it will be > destroyed. (I just tested the code and verified that the beancounter is > destroyed when the task dies). If a task created resource remains then the beancounter remains until the resources are destroyed, so it may exit well after the last task (eg an object handed to another process with a different luid is stil charged to us) > Let me reword the requirement: beancounter/resource group should _not_ > be destroyed implicitly. It should be destroyed only when requested by > the user/sysadmin. In other words, we need a create_luid() and > destroy_luid(). So that you can preserve the limits on the resource group ? That also makes sense if you are trying to do long term resource management. Alan - 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/