From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] restore scheduler priority for udev children
Date: Sun, 26 Jun 2005 17:13:00 +0000 [thread overview]
Message-ID: <20050626171300.GA5621@vrfy.org> (raw)
In-Reply-To: <20050626163800.GA9511@wonderland.linux.it>
On Sun, Jun 26, 2005 at 06:38:00PM +0200, Marco d'Itri wrote:
> udevd has a nice level of -4, which is inherited by spawned children.
No, the childrens get an explicit level.
> This patch restores the usual level of 0, to help mitigating the effects
> of broken processes which consume all the available CPU.
>
> (I don't know the real cause, I'm still investingating it, but the patch
> looks like a good idea anyway.)
Old versions of udevd+event scripts started from udevsend had all a
inherited nice level of -5 and therefore this was added. Just set the
values in udevd.h, if you think they should be different:
#define UDEVD_PRIORITY -4
#define UDEV_PRIORITY -2
Kay
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-06-26 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 16:38 [PATCH] restore scheduler priority for udev children Marco d'Itri
2005-06-26 17:13 ` 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=20050626171300.GA5621@vrfy.org \
--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).