All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Paul Larson <plars@austin.ibm.com>,
	marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
	manfred@colorfullife.com
Subject: Re: [PATCH] 2.4.18-rc2 Fix for get_pid hang
Date: Fri, 22 Feb 2002 16:41:43 -0800	[thread overview]
Message-ID: <20020223004143.GL3511@holomorphy.com> (raw)
In-Reply-To: <1014416988.12007.461.camel@plars.austin.ibm.com> <E16eQ4R-0003cZ-00@the-village.bc.nu>
In-Reply-To: <E16eQ4R-0003cZ-00@the-village.bc.nu>

At some point in the past, Paul Larson wrote:
>> This was made against 2.4.18-rc2 but applies cleanly against
>> 2.4.18-rc4.  This is a fix for a problem where if we run out of
>> available pids, get_pid will hang the system while it searches
>> through the tasks for an available pid forever.

On Sat, Feb 23, 2002 at 12:29:47AM +0000, Alan Cox wrote:
> Wouldn't it be a much cleaner patch to limit the maximum number of
> processes to less than the number of pids available. You seem to be
> fixing a non problem by adding branches to the innards of a loop.

I've seen this one before. It seems to kick in at 11K processes, where
one would normally expect it much higher... so I'm not sure a constant
upper bound on that counter suffices. Maybe clashes of pid's with pgrp's
and sessions and tgrps are what does that, maybe it's something else.

and of course:

#include <stdgeek.h>  /* Any hope of a non-O(tasks) solution? */


Cheers,
Bill

  parent reply	other threads:[~2002-02-23  0:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 22:29 [PATCH] 2.4.18-rc2 Fix for get_pid hang Paul Larson
2002-02-23  0:29 ` Alan Cox
2002-02-23  0:26   ` Rik van Riel
2002-02-23  0:41   ` William Lee Irwin III [this message]
2002-02-25 13:41   ` Paul Larson
2002-02-25 14:20     ` Alan Cox

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=20020223004143.GL3511@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=marcelo@conectiva.com.br \
    --cc=plars@austin.ibm.com \
    /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.