Re: [RFC v1 0/3] driver-core: add asynch module loading support
From: Tejun Heo
Date: Sun Aug 31 2014 - 06:14:26 EST
I haven't followed the previous discussions so please let me know if
this has been discussed before. It looks like you're trying to extend
the async mechanism and applying them to init functions themselves.
That sounds kinda weird to me. Isn't the root cause of the problem
doing device probings along with driver initilaization on module load?
Wouldn't it be more logical to simply make bus_add_driver() ->
driver_attach() invocation asynchronous? There's no reason to make
them parallel either. We can use an ordered queue for it so that we
don't lose the probing order we used to have. Making things go
parallel is the responsibility of each probing function after all and
there isn't much to gain by making attach calls go parallel.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/