From: Mike Travis <travis@sgi.com>
To: Rik van Riel <riel@redhat.com>
Cc: Hedi Berriche <hedi@sgi.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jack Steiner <steiner@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
Robin Holt <holt@sgi.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v2
Date: Wed, 21 Apr 2010 10:54:22 -0700 [thread overview]
Message-ID: <4BCF3BCE.7050906@sgi.com> (raw)
In-Reply-To: <4BCF336B.1050706@redhat.com>
Rik van Riel wrote:
> On 04/21/2010 12:59 PM, Hedi Berriche wrote:
>> On Wed, Apr 21, 2010 at 10:20 Alan Cox wrote:
>> |> of 32k will not be enough. A system with 1664 CPU's, there are
>> 25163 processes
>> |> started before the login prompt. It's estimated that with 2048
>> CPU's we will pass
>> |
>> | Is that perhaps the bug not the 32K limit?
>>
>> Doubt it: I just checked on an *idle* 1664 CPUs system and I can see
>> 26844
>> tasks, all but few being kernel threads.
>
> That is 15 kernel threads per CPU.
>
> Reducing the number of kernel threads sounds like a
> useful thing to do.
I'm doing more research but all the udev modprobes seem to spawn
quite a few tasks. And even though they go away, when the pid
pool is limited, I'm guessing many of them are waiting.
On the last test I did yesterday, the pid # was up in the 77000
range at the login prompt (I started the 1664 cpu system with
pid_max=128k).
next prev parent reply other threads:[~2010-04-21 17:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 1:40 [Patch 1/1] init: Provide a kernel start parameter to increase pid_max Mike Travis
2010-04-21 1:52 ` [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v2 Mike Travis
2010-04-21 9:23 ` Alan Cox
2010-04-21 16:59 ` Hedi Berriche
2010-04-21 17:18 ` Rik van Riel
2010-04-21 17:54 ` Mike Travis [this message]
2010-04-21 19:14 ` John Stoffel
2010-04-21 19:33 ` Hedi Berriche
2010-04-21 20:10 ` John Stoffel
2010-04-21 22:24 ` Greg KH
2010-04-21 22:49 ` Rik van Riel
2010-04-21 23:22 ` Greg KH
2010-04-22 9:28 ` Alan Cox
2010-04-22 12:58 ` Jack Steiner
2010-04-22 13:57 ` Robin Holt
2010-04-22 14:48 ` Linus Torvalds
2010-04-22 17:08 ` Robin Holt
2010-04-22 18:10 ` John Stoffel
2010-04-22 20:35 ` Andrew Morton
2010-04-25 7:16 ` Pavel Machek
2010-04-25 17:15 ` Linus Torvalds
2010-04-25 17:27 ` Linus Torvalds
2010-04-25 12:13 ` Pavel Machek
2010-04-26 19:48 ` [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v3 Mike Travis
2010-04-26 20:46 ` Greg KH
2010-04-27 0:43 ` Mike Travis
2010-04-27 0:42 ` [Patch 1/1] init: Increase pid_max based on num_possible_cpus v4 Mike Travis
2010-04-21 17:58 ` [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v2 Alan Cox
2010-04-21 19:12 ` Hedi Berriche
2010-04-21 19:51 ` Greg KH
2010-04-21 20:12 ` Hedi Berriche
2010-04-21 22:05 ` Jack Steiner
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=4BCF3BCE.7050906@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hedi@sgi.com \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
--cc=steiner@sgi.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.