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: udev-059 and default.hotplug script
Date: Sun, 03 Jul 2005 19:46:37 +0000	[thread overview]
Message-ID: <20050703194637.GA1505@vrfy.org> (raw)
In-Reply-To: <20050702012817.46255.qmail@web30214.mail.mud.yahoo.com>

On Sun, Jul 03, 2005 at 06:26:29PM +0200, Marco d'Itri wrote:
> 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).

Is there anything else than adding modalias support to udevstart to
replace what coldplug is doing today? But hey, this also only works
with 2.6.12 too. :)

> > 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?

Sure, that's the plan and already works that way, but with kernels older
2.6.12, udevd would need to read the "dev" file in sysfs and the sysfs
files may arrive at any time later cause of bad sysfs-timing. So we
would need wait_for_sysfs in the daemon with stat() loops for concurrent
events in parallel compared to just use $MAJOR/$MINOR from the netlink event.
I don't say that this is impossible, but it definitely is a total mess.

With netlink, modalias and $MAJOR/$MINOR, only available after 2.6.11/2.6.12,
there is a good reason to drop old kernel-versions.

Thanks,
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

  parent reply	other threads:[~2005-07-03 19:46 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
2005-07-03 19:46 ` Kay Sievers [this message]
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=20050703194637.GA1505@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).