On Mon, Jul 10, 2006 at 11:18:04AM +1200, Michal Ludvig wrote: > > How would autoload work then? If we have all sha1-capable modules loaded > in the kernel first we could then pick the one that offers sha1 w/o > fallback (i.e. sha1-generic). But how to tell which module to autoload > if they are not in the memory?
I don't have an easy answer for that. However, it should be no worse than what we have now. That is, padlock-sha would load shax-generic if it fails to allocate a fallback by the REQUIRES_FALLBACK flag. If the user wishes to use a better fallback, then they can load that module directly, much the same as specifying it through a module parameter. Actually, it's slightly better than the module parameter in that they can do it even after padlock-sha has been loaded. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
