> Not modprobe, but the crypto subsystem. If you have the generic C code
> and the assembly variant it picks the assembly over C. The selection is
But only if they're both loaded. Who loads both?
> In that case yes. Would it help to add MODULE_ALIAS("aes") to the
> assembly version in order to load it (atleast both)?
No, modprobe will only load the first it finds.
> >Also if one implementation is always better than the other
> >then I see little reason to ever have both.
>
> If you are sure that nobody needs aes on machnies prio i586 than you
> could disable the generic version on i386.
Why should the i586 version not run on 486/386?
> BUT: you might get into some trouble if you remove it from selections
> because some modules select it automaticly, IEEE80211_CRYPT_CCMP for
> instance.
Ok that is a problem.
-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
