On Wed, May 13, 2009 at 07:08:26AM -0400, Neil Horman wrote: > > Not really sure I agree with the logic here. I agree that its pretty clear that > its major value is for quickly testing all the algorithms in a system, but > universally failing the loading of the module simply to save a few milliseconds > seems like a poor choice. In so doing you create an alias effect, as jarod > noted between a non-existent module and a module that failed to load. The > aliasing can be resolved, if you want to parse dmesg, but if speed is the issue > at hand, that parsing is a significant impact. If you allow the module to load > properly, then for the cost of an rmmod, you can tell simply from the exit code > of modprobe: > 1) If the module was found > 2) If the tests passed As I said, tcrypt should no longer be used to test algorithms. Algorithms are tested as they load, with the result available in /proc/crypto. tcrypt is just a relic that will be going away. Do not rely on it. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
