Date: Thu, 05 Feb 2004 21:54:55 +0800 From: "Jun Su" <junsu@delphij.net> To: "Peter Jeremy" <PeterJeremy@optushome.com.au> Cc: current@freebsd.org Subject: [UPDATE] new pid allocation patch (was: Call for testers: New PID allocator patch for -CURRENT) Message-ID: <opr2wgxta1l8p7vk@mail.frontfree.net> In-Reply-To: <20040131215006.GP908@cirb503493.alcatel.com.au> References: <20040129134121.GB53644@frontfree.net> <20040129200442.GA52780@VARK.homeunix.com> <01bd01c3e742$093d83b0$56dea1d3@shasujunmv> <20040131215006.GP908@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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. Thanks, Jun Su
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opr2wgxta1l8p7vk>