On 2 April 2013 12:35, Sergey Yanovich <ynvich@xxxxxxxxx> wrote: > On Tue, 2013-04-02 at 12:13 +0200, Ulf Hansson wrote: >> Consider a platform having two eMMCs and one SD-card. Each eMMC card >> will take around 400 ms to initialize and the SD-card 700 ms. The card >> initialization times are real examples from eMMCs and SD-cards, >> moreover those are typical values not worth cases. In total we have >> around 1.5 s to initialize the cards. > > We have a separate workqueue per host, so all probes go in parallel. > They also go in parallel with probing for other devices. So the actual > delay is 700 ms minus maximum probing time for other devices. The time > is either zero or small (dozen us) on the hardware I have access to > (intel laptop, arm controller). > >> Now, suppose you boot using an initrd image. Thus neither of the cards >> needs to be accessible immediately after the kernel has booted. It all >> depends what the init process decides to do. With this patch the init >> process will always be delayed to wait for each and every card to be >> initialized. I would prefer a solution where this can be configurable >> somehow, since certainly this is not the scenario you want for all >> cases. > > If the system is booted using initrd and root is not on an mmc card, > then mmc modules can be omitted from initrd. The probing will happen > only after root is mounted. This will not solve the problem when having one device intended for rootfs and some other for something else. Of course, as long as the devices uses the same mmc module. Once inserted, all devices will be probed. > > If root is on an mmc, kernel needs to wait for the mmc probe. > True, although your patch is preventing the parallelism and instead doing things in synchronized manner. I think we must discuss alternative solutions instead. Like an "mmc detect flush" mechanism or a "new card device notification" event. Kind regards Ulf Hansson -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
