From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 07:41:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C16F16A4CE for ; Thu, 5 Feb 2004 07:41:30 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE24A43D53 for ; Thu, 5 Feb 2004 07:41:25 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 75544 invoked from network); 5 Feb 2004 15:41:24 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.47]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 5 Feb 2004 15:41:24 -0000 Message-ID: <40226429.4010702@freebsd.org> Date: Thu, 05 Feb 2004 16:41:29 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040125 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jun Su References: <20040129134121.GB53644@frontfree.net> <20040129200442.GA52780@VARK.homeunix.com> <01bd01c3e742$093d83b0$56dea1d3@shasujunmv> <20040131215006.GP908@cirb503493.alcatel.com.au> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Peter Jeremy cc: David Schultz cc: Olivier Houchard cc: current@freebsd.org Subject: Re: [UPDATE] new pid allocation patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 15:41:30 -0000 Jun Su wrote: > Hi All, > > John Baldwin's proc lock commit today made my patch broken, so I have > revised the patch, and uploaded it to the same position: > http://www.arbornet.org/~junsu/pid.diff > > The revised patch has been improved based on the feedback. Basically, > > 1. Added a new sysctl value kern.pidmax to control the current pid range. > This value can influence the reuse pid period. The initial value is 4096. This sysctl name looks very misleading to me. Unless the highest PID I can get here is actually 4096. > 2. Change the meaning of PID_MAX back to what it was, and sainty-check > whether the pid is 5 digit based on PID_MAX. (I think it is impossible that > pid expand PID_MAX for the algorithm nature, though.) > > 3. The initial pid table size is bumped from 1<<5 to 1<<7. -- Andre