All of lore.kernel.org
 help / color / mirror / Atom feed
From: iSteve <isteve@rulez.cz>
To: linux-kernel@vger.kernel.org
Subject: udevstart surprisingly slow
Date: Mon, 30 Jan 2006 23:04:14 +0100	[thread overview]
Message-ID: <43DE8D5E.2040905@rulez.cz> (raw)

Greetings,
I've recently upgraded udev from 063 to 082 and then 084.

With 063, startup of udev was near-instant; with both 082 and 084, it 
takes a significant ammount of time (~15s) to create the base devices 
using udevstart or udevsynthesize (this one is taken from Debian, which 
apparently in turn taken it from SuSE; the rest of codebase is vanilla).

This issue appears on kernel 2.6.15.1 with SquashFS 2.2r2, SWSUP2 2.2 
and VesaFB-TNG 1.0-rc1-r3 patches.

The init script used simply mounts 10MiB tmpfs onto /dev, creates 
/dev/.udev/{db,queue} directories, then runs udevd --daemon and then 
udevsynthesize or udevstart (tried both, same result).

I'm quite out of ideas, I don't think downgrading udev is the best 
solution, so I wonder: what takes such a long time in udevstart? What 
can I alter at my end, or is this a known bug (or feature)?

Thanks in advance for reply
  -- iSteve

             reply	other threads:[~2006-01-30 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 22:04 iSteve [this message]
2006-01-31  7:42 ` udevstart surprisingly slow Greg KH

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=43DE8D5E.2040905@rulez.cz \
    --to=isteve@rulez.cz \
    --cc=linux-kernel@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.