2009/5/20 Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>: > On 5/19/09, Ozan Çağlayan <ozan@xxxxxxxxxxxxx> wrote: >> 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. 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)? > 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. Kay -- 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
