Ingo Molnar <[EMAIL PROTECTED]> writes: > so 93.6% of the allyesconfig bootup time is in 2.5% of the initcalls. If > they were fixed then an allyesconfig bzImage, which would be capable to > run on every PC known to mankind without any module whatsoever, would
Assuming that every PC has enough memory @) Allyes is >35MB > take around 10 seconds to boot up (which is acceptable for kernel bootup > time). It might make sense to measure idle ticks vs busy ticks too. If it's idle cycles perhaps things can be more easily fixed by multi threading the initialization. If it's busy cycles perhaps they can be converted into sleeping cycles. Perhaps you should tell the individual maintainers for those? If they still have one. A lot of them look like old hardware where there might be no working ones left, perhaps just deprecation would make sense. > initcall 0xc1f5487d ran for 23083 msecs: pca_isa_init+0x0/0x143() > initcall 0xc1f54fba ran for 17121 msecs: pcf8574_init+0x0/0x20() e.g. those just look like bugs. > initcall 0xc1f0c06f ran for 14710 msecs: net_olddevs_init+0x0/0x169() That's many drivers initialized together for compatibility ordering reasons. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
