On Wed, 2010-09-22 at 16:06 -0600, Jason Gunthorpe wrote: > On Wed, Sep 22, 2010 at 02:38:31PM -0700, Nicholas A. Bellinger wrote: > > > So I think the main bit here is the ability to request > > crc32c-intel.ko first, and then fall back to crc32c.ko when the > > former is not available on CONFIG_X86. > > Well, it is what Andi said, everything is working fine but there is no > mechanism to autoload the accelerated crypto module. If you did > modprobe crc32c_intel prior to loading your driver it would > automatically get crc32c-intel when it asks for crc32c since it is > loaded and a higher priority. >
Ah, OK. I see what you mean now here wrt to libcrypto priorities and crc32c + crc32c_intel modules. My apologies for the in-experience with libcrypto here.. > So, the drivers are correct to just request crc32c .. The work around > to limited autoprobing is so trivial (modprob crc32_intel) I'm not > sure including extra autoprobing code in the drivers is worthwhile? > Indeed, I am happy to drop this patch if Bernard would be nice enough to add a 'modprobe crc32_intel' into the SIW scripts. Thanks for your comments Jason! --nab -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
