From owner-freebsd-hackers Tue Aug 29 11:04:00 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA17410 for hackers-outgoing; Tue, 29 Aug 1995 11:04:00 -0700 Received: from mpp.minn.net (mpp.Minn.Net [204.157.201.242]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id LAA17404 for ; Tue, 29 Aug 1995 11:03:56 -0700 Received: (from mpp@localhost) by mpp.minn.net (8.6.11/8.6.9) id NAA02791; Tue, 29 Aug 1995 13:02:33 -0500 From: Mike Pritchard Message-Id: <199508291802.NAA02791@mpp.minn.net> Subject: Re: 16-bit pids? (was Re: 16, 32, and 64bit types?) To: taob@gate.sinica.edu.tw (Brian Tao) Date: Tue, 29 Aug 1995 13:02:33 -0500 (CDT) Cc: hackers@freefall.FreeBSD.org In-Reply-To: from "Brian Tao" at Aug 30, 95 01:52:39 am X-Mailer: ELM [version 2.4 PL24 ME7a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 973 Sender: hackers-owner@FreeBSD.org Precedence: bulk Brian Tao wrote: > > On Mon, 28 Aug 1995, Mike Pritchard wrote: > > > > Since the subject of PID_MAX has come up, what is the reason > > for having it set to 30,000? That isn't really that large of > > a value, especially on a busy system. How about raising it to > > something like 90,000? > > Even if you had 1000 processes running on one system, that still > leaves 29000 pids free. Even forking off a new process 10 times a > second will still take you over 45 minutes to cycle through 29000 > pids... what's the point of having >30000 PID_MAX? In the past I've been involved in some projects where pid collisions due to pid wrap was a problem. I'm not currently doing anything that this is causing any problems with, but seeing the low limit reminded me of those past projects. In that case, the longer you could keep from re-using pids, the better. -- Mike Pritchard mpp@mpp.minn.net "Go that way. Really fast. If something gets in your way, turn"