linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: linux-hotplug@vger.kernel.org
Subject: Re: Debugging udevd startup time
Date: Wed, 20 May 2009 05:54:46 +0000	[thread overview]
Message-ID: <4A139B26.9020106@pardus.org.tr> (raw)
In-Reply-To: <4A1316C2.4090407@pardus.org.tr>

Kay Sievers wrote On 20-05-2009 03:12:
> Do  you use the latest module-init-tools, and created a binary index
> with depmod?
>
> How many modules do you need to load during boot (lsmod | wc -l)?
>   
36 modules are loaded during boot.

I'm using module-init-tools 3.8 and yes I have the following *.bin files
in /lib/modules:

modules.alias.bin
modules.dep.bin
modules.symbols.bin

>> One word: bootchart.  It should show you whether the process is
>> cpu-bound, IO-bound, or something else, AND hopefully see if any other
>> process has a significant impact.  It's fairly coarse grained, but if
>> you have some big problems then they should show up on it.
>>     
>
> 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.

Should I accept those timings and go on or should I be unhappy about
them and try to dig more?

I'll check the bootchart output but fairly I really hate its way of
drawing the booting sequence :)

Thanks a lot
Ozan Caglayan



  parent reply	other threads:[~2009-05-20  5:54 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 [this message]
2009-05-20 16:25 ` Ozan Çağlayan
2009-05-20 18:19 ` Greg KH
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=4A139B26.9020106@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --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).