From owner-p4-projects@FreeBSD.ORG Sun May 31 18:51:14 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id F131E1065675; Sun, 31 May 2009 18:51:13 +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 B1677106566C for ; Sun, 31 May 2009 18:51:13 +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 9A8CE8FC0C for ; Sun, 31 May 2009 18:51:13 +0000 (UTC) (envelope-from trasz@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n4VIpDro021433 for ; Sun, 31 May 2009 18:51:13 GMT (envelope-from trasz@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n4VIpDUs021431 for perforce@freebsd.org; Sun, 31 May 2009 18:51:13 GMT (envelope-from trasz@freebsd.org) Date: Sun, 31 May 2009 18:51:13 GMT Message-Id: <200905311851.n4VIpDUs021431@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 Cc: Subject: PERFORCE change 163191 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2009 18:51:14 -0000 http://perforce.freebsd.org/chv.cgi?CH=163191 Change 163191 by trasz@trasz_victim on 2009/05/31 18:50:40 Revise the milestones. Affected files ... .. //depot/projects/soc2009/trasz_limits/MILESTONES#2 edit Differences ... ==== //depot/projects/soc2009/trasz_limits/MILESTONES#2 (text+ko) ==== @@ -1,15 +1,17 @@ 0. Figure a good name. "Resources" is not a good name, as it's already being used for newbus. -1. Add nmount(2)-like API to get and set limits. +1. Add some API to communicate between kernel and the userland. + + <--- WE ARE HERE ---> -2. Add macros/routines to allocate and free resources. +2. Userland tools - either modify limits(1) or implement something new. -3. Userland tools - either modify limits(1) or implement something new. +3. Add macros/routines to allocate and free resources. 4. Add calls to resource allocation and free routines all over the place. -5. Make resources hierarchical. +5. Revise the API to be extensible, e.g. nmount(2)-like. 6. Make things fast.