* Herbert Xu | 2007-08-20 20:06:05 [+0800]: >On Mon, Aug 20, 2007 at 12:16:18PM +0200, Andi Kleen wrote: >> I don't think modprobe knows anything about these priorities. > >Right, in that case we'd only load one of them, usually >the generic one since its name is what we're trying to >load. > >> But that would require teaching the module loading user space >> about all this first, right? > >That would be the best. However, it's not hard to do a >simple probing in the kernel until modprobe(8) gets this >feature. > >I'll code something up.
Herbert, I tried to implement a MODULE_PRIO() macro which would be used by the module loader and I noticed that it may not be required. If there are two modules providing the same alias and we modprobe that alias than modprobe will load both of them. It may be a waste of memory if we load the generic algorithm and the assembly optimized one. However, it would be good for some hardware drivers which need the generic implementation for some "corner cases". What do you thing? Sebastian - 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
