> For you, based on the bootchart, it looks like modprobe is actually > loading modules. and the time to do (a) is insignificant compared to (b) > and (c). It's probably taking most of time in (c) which means kernel is > working and initialising the module and possibly hardware. It's probably > non-trivial to try to improve your situation. > > - Timo >
According to strace, init_module is responsible for 85-95% of the time (depending on the module), but the rest is practically all from read. While fixing this issue wouldn't make a huge difference in my case, it would seem to have a measurable effect nonetheless. I guess for the big effect I should wait for the mentioned module loader work. - Lauri -- http://www.fastmail.fm - A no graphics, no pop-ups email service _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox
