From owner-p4-projects@FreeBSD.ORG Sat Aug 7 11:03:25 2010 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 331D71065677; Sat, 7 Aug 2010 11:03:25 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA4B2106566B for ; Sat, 7 Aug 2010 11:03:24 +0000 (UTC) (envelope-from trasz@freebsd.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id D80518FC19 for ; Sat, 7 Aug 2010 11:03:24 +0000 (UTC) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.4/8.14.4) with ESMTP id o77B3Oxc071751 for ; Sat, 7 Aug 2010 11:03:24 GMT (envelope-from trasz@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.4/8.14.4/Submit) id o77B3OxN071749 for perforce@freebsd.org; Sat, 7 Aug 2010 11:03:24 GMT (envelope-from trasz@freebsd.org) Date: Sat, 7 Aug 2010 11:03:24 GMT Message-Id: <201008071103.o77B3OxN071749@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to trasz@freebsd.org using -f From: Edward Tomasz Napierala To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 182010 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Aug 2010 11:03:25 -0000 http://p4web.freebsd.org/@@182010?ac=10 Change 182010 by trasz@trasz_victim on 2010/08/07 11:03:10 Make sure to not forget about P_SYSTEM issue. Affected files ... .. //depot/projects/soc2009/trasz_limits/TODO#20 edit Differences ... ==== //depot/projects/soc2009/trasz_limits/TODO#20 (text+ko) ==== @@ -37,6 +37,14 @@ - per-jail containers - per-jail resource limits +Issues: + + - Don't account resources for system processes. It's not as easy as checking + for P_SYSTEM flag, as the flag will be set for AIO kernel processes. + + Also, try to figure out what's going on with 'intr' p_flag - checking for P_SYSTEM + didn't really work for that process. + HRL-specific issues: - Bring back per-group limits.