From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: UDev startup 30-45s or more
Date: Tue, 07 Feb 2006 12:56:49 +0000 [thread overview]
Message-ID: <20060207125649.GB10208@vrfy.org> (raw)
In-Reply-To: <43E896DB.2080506@rulez.cz>
On Tue, Feb 07, 2006 at 01:47:23PM +0100, iSteve wrote:
> Greetings,
> I've recently upgraded udev from 069 onto 084, and kernel from 2.6.13
> onto 2.6.15.1.
>
> For coldplugging, I've implemented the init script mentioned on this
> mailing list, which writes "add" into uevent file for everything I want
> to have recognized by udev, ie. /sys/bus/*/devices/*/uevent
> /sys/class/*/*/uevent /sys/block/*/uevent /sys/block/*/*/uevent. This is
> approx. 700 files.
>
> Writing into all these files already takes approx. 10-15s, but I do not
> mind that, as I believe that can be optimised later.
>
> What I consider troublesome is that processing the queue takes over 20
> more seconds, totalling at about 30-45 seconds, which is more than all
> other init scripts altogether. I wonder, how can I optimise it? What am
> I doing wrong?
>
> The init script creates /dev on tmpfs (the rootfs is read-only), runs
> udev --daemon and writes 'add' in correct order (as used on the init
> script posted on this mailing list) into the uevent files. Then waits 20
> seconds or until /dev/.udev/queue disappears, whichever comes first
> (unfortunately, /dev/.udev/queue doesn't disappear in the given time).
>
> I am using udev to load modules as well, however, it has no effect if I
> have loaded them prior to running udev.
No idea. On my 2GHz laptop, the whole coldplug with running the full setup
for all ~400 devices and creating all nodes takes ~2 seconds until the queue
is completely empty.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-02-07 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 12:47 UDev startup 30-45s or more iSteve
2006-02-07 12:56 ` Kay Sievers [this message]
2006-02-07 14:43 ` iSteve
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=20060207125649.GB10208@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 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.