From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-059 and default.hotplug script
Date: Sun, 03 Jul 2005 16:26:29 +0000 [thread overview]
Message-ID: <20050703162629.GA13401@wonderland.linux.it> (raw)
In-Reply-To: <20050702012817.46255.qmail@web30214.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Jul 03, Kay Sievers <kay.sievers@vrfy.org> wrote:
> But we need to walk through /sys/devices to catch devices there
> for modules-load, ..., right? That is not handled by udevstart
> currently.
udevstart should walk /sys/bus/*/devices/ to support $MODALIAS (look at
my modalias.rc).
> On event replay you fire ~800 processes in a few seconds, while most of
> these events are simple devices without any further processing. Tests showed
> and my coworkers needed to convince me that doing this in-process is much
> faster and you save some seconds bootup-time. (using udevstart does not have
> this problem, cause it already does everything with only one process)
Why not move the whole udev in udevd then, and make it fork and continue
processing only when needed?
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-03 16:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 1:28 udev-059 and default.hotplug script Phil K
2005-07-02 2:46 ` Greg KH
2005-07-02 8:22 ` Marco d'Itri
2005-07-02 15:55 ` Greg KH
2005-07-02 15:58 ` Greg KH
2005-07-02 16:21 ` Marco d'Itri
2005-07-02 18:59 ` Stefan Schweizer
2005-07-02 19:06 ` Greg KH
2005-07-02 19:37 ` Kay Sievers
2005-07-03 7:17 ` Greg KH
2005-07-03 7:20 ` Greg KH
2005-07-03 10:22 ` Marco d'Itri
2005-07-03 10:53 ` Kay Sievers
2005-07-03 12:15 ` Marco d'Itri
2005-07-03 14:01 ` Kay Sievers
2005-07-03 16:26 ` Marco d'Itri [this message]
2005-07-03 19:46 ` Kay Sievers
2005-07-03 20:15 ` Marco d'Itri
2005-07-03 21:02 ` Kay Sievers
2005-07-05 10:28 ` Marco d'Itri
2005-07-05 11:45 ` Kay Sievers
2005-07-05 11:50 ` Marco d'Itri
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=20050703162629.GA13401@wonderland.linux.it \
--to=md@linux.it \
--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).