linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd - throttle fork() if we get to many childs in running
Date: Mon, 17 Jan 2005 19:16:11 +0000	[thread overview]
Message-ID: <1105989371.6336.160.camel@localhost.localdomain> (raw)
In-Reply-To: <1104030808.5805.34.camel@localhost.localdomain>

On Mon, 2005-01-17 at 10:52 -0800, Patrick Mansfield wrote:
> Hi Kay -
> 
> On Sun, Jan 16, 2005 at 05:16:39PM +0100, Kay Sievers wrote:
> 
> >   If the system reaches a defined limit of processes in running state, udevd
> >   starts to count its own processes in running state from its session (all
> >   forked hotplug child processes, subprocesses and callouts) and throttles
> >   further process forking if the limit is reached.
> 
> Why do you only count running processes? Seems a bit abitrary, since you
> don't know when the sleeping processes will become runnable.

Good question! :)

Hmm, yes it's not a hard limit. If we reach the running maximum, we at
least don't fork more childs. My tests with the scsi_debug and a killer-
hotplug-script worked very nice that way.

> Why not increase the total limit, and count all of its processes? I
> doubt that would change timings.

The current scripts use sleep calls and I thought it would be nice to
let other processes run if they do nothing in the meantime.

Some stupid script may completely block the hotplug handling just by
sleeping for a long time with that hard limit.

Thanks,
Kay



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2005-01-17 19:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-26  3:13 udevd - throttle fork() if we get to many childs in running Kay Sievers
2005-01-16 16:16 ` Kay Sievers
2005-01-17 18:52 ` udevd - throttle fork() if we get to many childs in running state Patrick Mansfield
2005-01-17 19:16 ` Kay Sievers [this message]

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=1105989371.6336.160.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.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 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).