From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?T3phbiDDh2HEn2xheWFu?= Date: Wed, 20 May 2009 05:54:46 +0000 Subject: Re: Debugging udevd startup time Message-Id: <4A139B26.9020106@pardus.org.tr> List-Id: References: <4A1316C2.4090407@pardus.org.tr> In-Reply-To: <4A1316C2.4090407@pardus.org.tr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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