linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Debugging udevd startup time
Date: Wed, 20 May 2009 18:19:26 +0000	[thread overview]
Message-ID: <20090520181926.GA4643@kroah.com> (raw)
In-Reply-To: <4A1316C2.4090407@pardus.org.tr>

On Wed, May 20, 2009 at 07:25:16PM +0300, Ozan Çağlayan wrote:
> Ozan Çağlayan wrote:
> >> The log shows 1.8 seconds, bootchart might not show too much here.
> >>   
> >>     
> >
> > I've just tried on a tiny sony vaio centrino laptop which loads 71
> > modules during boot. Its log shows 1.4 seconds between the first and the
> > last event.
> >   
> 
> 3.2 seconds on a recent Dual Core MacbookPro5,1 which loads 52 modules
> during boot. It seems that the gap can oscillate very brutally from one
> system to another one.

That sounds like a modprobe issue, not a udev one.

There have been some new kernel changes to make this go faster, perhaps
you need to integrate them.  Also realize that loading 52 modules will
take a lot of time, just due to all of the in-kernel lookups that are
necessary to accomplish this.

Perhaps you might wish to cut down on this large number, if you have
everything as modules, you loose some of the new kernel speedups that
have happened with async probing of devices which can not happen if the
drivers are in modules.

Look at the recent moblin releases for examples of how to speed this up.

good luck,

greg k-h

  parent reply	other threads:[~2009-05-20 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 20:29 Debugging udevd startup time Ozan Çağlayan
2009-05-19 23:36 ` Alan Jenkins
2009-05-20  0:12 ` Kay Sievers
2009-05-20  5:54 ` Ozan Çağlayan
2009-05-20 16:25 ` Ozan Çağlayan
2009-05-20 18:19 ` Greg KH [this message]
2009-05-20 18:27 ` Kay Sievers
2009-05-20 19:25 ` Ozan Çağlayan

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=20090520181926.GA4643@kroah.com \
    --to=greg@kroah.com \
    --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).