linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Frederick, Fabian" <Fabian.Frederick@prov-liege.be>
Cc: "Linux-Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: pid_max ?
Date: Thu, 31 Jul 2003 14:23:42 -0700	[thread overview]
Message-ID: <20030731212342.GE15452@holomorphy.com> (raw)
In-Reply-To: <D9B4591FDBACD411B01E00508BB33C1B01BF8C95@mesadm.epl.prov-liege.be>

On Wed, Jul 30, 2003 at 09:53:12AM +0200, Frederick, Fabian wrote:
> 	I was looking at pid.c file and can't understand pid_max usage.
> It's defined as integer (signed) =PID_MAX_DEFAULT (which is 0x8000 (on old
> arch, integer max positive value isn't 32767 ? so 0x8000 -> -32768).
> 	In alloc_pidmap, 'if (pid>=pid_max)' should be in that case always
> true so pid=RESERVED_PIDS which is 300 (?).Why not use pid>PID_MAX_DEFAULT
> there and forget the pid_max definition ? and why do we have that '300'
> value ?

It's to avoid trying to allocate from the range of pid's typically used
by kernel threads and system daemons after bootup. There are no hard
dependencies on it, it's merely "traditional pidspace layout".


-- wli

      reply	other threads:[~2003-07-31 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  7:53 pid_max ? Frederick, Fabian
2003-07-31 21:23 ` William Lee Irwin III [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030731212342.GE15452@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=Fabian.Frederick@prov-liege.be \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).