| |||||||||||||
|
| |||||||||||||
Bits from the Debian Eee PC teamBits from the Debian Eee PC teamPosted Oct 15, 2008 20:30 UTC (Wed) by nix (subscriber, #2304)In reply to: Bits from the Debian Eee PC team by endecotp Parent article: Bits from the Debian Eee PC team
If you're using the default rules, it's probably calling modprobe a bunch
of times for modules you don't have.
(Log in to post comments)
Bits from the Debian Eee PC team Posted Oct 15, 2008 21:32 UTC (Wed) by endecotp (guest, #36428) [Link]
Everything that it needs is built in to the kernel. I have the impression that during coldplug it still calls modprobe, but that that's a no-op as no module is loaded. I'm not sure how much time is spent doing that and whether it's worth trying to fix it; it's clearly spending more time bringing up the network, which could be postponed until later in the boot and run asynchronously.
If anyone's curious, I have put bootgraph/chart here which you can compare with Arjan's from his LPC presentation:
http://chezphil.org/tmp/bootgraph1.svg
Bits from the Debian Eee PC team Posted Oct 15, 2008 22:02 UTC (Wed) by nix (subscriber, #2304) [Link]
It eliminates dozens of forks, at least, and if you know you have no
modules that's all wasted time. (It takes nearly a second to do those modprobes on my 1.2GHz Athlon IV.)
|
|
||||||||||||
