On 5/19/09, Ozan Çağlayan <ozan@xxxxxxxxxxxxx> wrote: > Hi, > > I wonder how can I debug the possible bottleneck(s) during the startup > of udevd? > > I'm writing the $(udevadm --monitor)'s output to a log file during boot > and I have the exact events and timestamps. I really don't understand > why the whole process takes a bunch of seconds. > > I'm using 2.6.30_rc6 + udev 141. > > It's a typical default udev installation. (compiled with -O2), > > Any help or comment on the subject would be really appreciated, I'm also > sending a link to the complete monitor.log: > > http://cekirdek.pardus.org.tr/~ozan/udevmonitor.log 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. There is also a specific script to analyse the timings in a monitor log, I haven't tried it myself though. <https://lists.launchpad.net/ubuntu-boot/msg00002.html>. Note that it's normal for udev startup to take a few seconds on a netbook-level processor. It's fair to say udev still has a little room for optimisation :-). Regards Alan -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
