From owner-soc-status@FreeBSD.ORG Fri Jun 5 18:53:57 2009 Return-Path: Delivered-To: soc-status@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26913106566B for ; Fri, 5 Jun 2009 18:53:57 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from pin.if.uz.zgora.pl (pin.if.uz.zgora.pl [212.109.128.251]) by mx1.freebsd.org (Postfix) with ESMTP id DED928FC08 for ; Fri, 5 Jun 2009 18:53:56 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: by pin.if.uz.zgora.pl (Postfix, from userid 1001) id D5A7539BA2; Fri, 5 Jun 2009 20:42:31 +0200 (CEST) Date: Fri, 5 Jun 2009 20:42:31 +0200 From: Edward Tomasz Napierala To: soc-status@FreeBSD.org Message-ID: <20090605184231.GB82492@pin.if.uz.zgora.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Subject: Hierarchical Resource Limits - status 1 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2009 18:53:57 -0000 The aim of my project is to gather all the resource limits (except disk quotas) in one place, and allow the system administrator to easily set rules to control it. So far, I've created a temporary, simple tool (called 'hrl') to display the ruleset, added a temporary, simple syscall interface to support it, modified kern_setrlimit() so that the resource limits end up in the HRL ruleset, and added some code to the kernel to actually store them and remove when the process exits. Most of the time was spent figuring out how to put all this together, and I still need some ideas. Next step is to add proper per-proccess resource accounting and start putting hrl_alloc() and hrl_free() in various places in the kernel. -- If you cut off my head, what would I say? Me and my head, or me and my body?