On Sat, 2013-07-20 at 09:24 +1000, Herbert Xu wrote: > On Fri, Jul 19, 2013 at 04:21:09PM -0700, H. Peter Anvin wrote: > > > > The issue here seems to be the dynamic binding nature of the crypto > > subsystem. When something needs crypto, it will request the appropriate > > crypto module (e.g. crct10dif), which may race with detecting a specific > > hardware accelerator based on CPUID or device information (e.g. > > crct10dif_pclmul). > > > > RAID has effectively the same issue, and we just "solved" it by > > compiling in all the accelerators into the top-level module. > > I think for crypto the simplest solution is to not do CPUID-based > loading. Then crypto users will simply load the module alias which > causes modprobe to load all modules providing that alias. > > Cheers, Herbert, I've tried the module alias approach (see my earlier mail with patch) but it didn't seem to load things properly. Can you check to see if there's anything I did incorrectly. Tim -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
