From owner-soc-status@FreeBSD.ORG Tue Jun 30 17:25:54 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 530E31065670 for ; Tue, 30 Jun 2009 17:25:54 +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 178188FC24 for ; Tue, 30 Jun 2009 17:25:54 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: by pin.if.uz.zgora.pl (Postfix, from userid 1001) id 5D90039BA3; Tue, 30 Jun 2009 19:27:49 +0200 (CEST) Date: Tue, 30 Jun 2009 19:27:49 +0200 From: Edward Tomasz Napierala To: soc-status@FreeBSD.org Message-ID: <20090630172749.GA90893@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 3 & 4 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: Tue, 30 Jun 2009 17:25:54 -0000 For the last two weeks I've reworked the syscall mechanism to pass strings instead of binary structures, worked on rule filtering, so that one can display only a few specific rules, or remove more than one rule. I'm pretty happy with ruleset management at this point, actually. I've also did some work on file descriptors and memory usage accounting. Next thing to do is to track down a problem that makes resource usage counters go negative and then enable limit enforcement and see what happens. -- If you cut off my head, what would I say? Me and my head, or me and my body?