> Are you sure you get the C version when both are built-in > or loaded as modules? If so then we have a bug in the priority > code.
The usual use case is: Somebody -- either admin or some command implicitely -- executes modprobe aes because some text file specifies the aes cipher. At least on my system that loads the C version when both are enabled. modprobe will not load multiple modules in this case. I don't think modprobe knows anything about these priorities. > We don't, but the system is meant to allow multiple > implementations to coexist and picking the best one > at run-time. But that would require teaching the module loading user space about all this first, right? Also if one implementation is always better than the other then I see little reason to ever have both. -Andi - 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
