linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Issue with max_threads (and other resources) and highmem
Date: Tue, 23 Oct 2001 17:00:17 -0700	[thread overview]
Message-ID: <3BD60491.25152E6C@kegel.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110232134470.3690-100000@imladris.surriel.com>

Rik van Riel wrote:
> 
> On Tue, 23 Oct 2001, Dan Kegel wrote:
> > Rik wrote:
> > > ... A sane upper limit for
> > > max_threads would be 10000, this also keeps in mind the
> > > fact that we only have 32000 possible PIDs, some of which
> > > could be taken by task groups, etc...
> >
> > ?  I thought the 2.4 kernel had switched to 32 bit pid's long ago.
> > Where does the limit of 32000 possible PIDs come from?
> 
> Please take a look at kernel/fork.c::get_pid() ...

Yes, I see the limit is enforced there, but why do we need that limit?

There are probably a bunch of user-space programs that assume
a pid fits in five digits, is that the main reason?
- Dan

  reply	other threads:[~2001-10-23 23:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23 23:30 Issue with max_threads (and other resources) and highmem Dan Kegel
2001-10-23 23:35 ` Rik van Riel
2001-10-24  0:00   ` Dan Kegel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23 20:19 Dave McCracken
2001-10-23 20:36 ` Andi Kleen
2001-10-23 20:46 ` Dave McCracken
2001-10-23 20:52 ` Rik van Riel
2001-10-23 21:05   ` Dave McCracken
2001-10-23 21:59     ` Rik van Riel

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=3BD60491.25152E6C@kegel.com \
    --to=dank@kegel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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).