Re: minor bugs around fork_init

Pavel Machek wrote: > > Hi! > > > > * get_pid causes a deadlock when all pid numbers are in use. > > > In the worst case, only 10900 threads are required to exhaust > > > the 15 bit pid space. > > > > Yes. I posted a patch for 31-bit pids once or twice. > > There is no great hurry, but on the ot

Re: minor bugs around fork_init

Hi! > > * get_pid causes a deadlock when all pid numbers are in use. > > In the worst case, only 10900 threads are required to exhaust > > the 15 bit pid space. > > Yes. I posted a patch for 31-bit pids once or twice. > There is no great hurry, but on the other hand, it is always > better to mak

Re: minor bugs around fork_init

On Sat, Dec 23, 2000 at 05:33:55PM +0100, Manfred wrote: > * get_pid causes a deadlock when all pid numbers are in use. > In the worst case, only 10900 threads are required to exhaust > the 15 bit pid space. Yes. I posted a patch for 31-bit pids once or twice. There is no great hurry, but on the

minor bugs around fork_init

I found 4 minor problems in the thread creation code: * 2.2 reserved 4 threads for root, and 2.4 still has the define (MIN_THREADS_LEFT_FOR_ROOT), but the code is missing :-( * get_pid causes a deadlock when all pid numbers are in use. In the worst case, only 10900 threads are required to exhaus