[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: more about proc

From: Marcus Brinkmann
Subject: Re: more about proc
Date: Wed, 15 Aug 2001 07:29:15 +0200
User-agent: Mutt/1.3.20i

On Wed, Aug 15, 2001 at 12:32:20AM -0400, Roland McGrath wrote:
> It's a good bet the bug is in libihash/ihash.c, since that creates a large
> array of chars on the stack and sets them all to 1 or 0.  

I am just thinking, if the stack size of a Mach thread is 16 pages = 65 kb
(is it?), and some other bug causes libihash to grow the hash tables very
fast (in the order of the number of processes ever registered, rather than
the number of living processes), as I observed it, then:

In this case, with about 60000 processes ever, and libihash on the
lookout for the next prime, the sieve allocated on the stack would be as
large as the stack or larger, wouldn't it?

So my current working hypothesis is that there are two bugs:
* pidhash is growing abnormally
* sieve is allocated on the stack, which is rather small for a Mach thread

However, the real bug is the first one, as 30000 processes and more running
at the same time would cause other resource shortages as well.


`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]