Re: {twofish,aes}-{x86_64,i586} versus C implementations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Herbert Xu | 2007-09-19 20:29:43 [+0800]:

>On Mon, Sep 03, 2007 at 12:42:27AM +0200, Sebastian Siewior wrote:
>>
>> [crypto] do not use generic AES on i386 and x86_64
>> 
>> This patch automatically selects the assembly optimized version
>> of AES (if selected) and the generic version can no longer be
>> selected. The module will be called aes.ko
>
>You don't need to rename it because it already provides an
>alias for aes.

Right, forgot about that.

>Also please provide a way to build the generic AES code so
>that it can at least be tested on i386/x86_64.

You want to auto compile aes-x86_64 if you are on x86_64 and additonally
the generic version. Is that correct?
If so, why do you want to have them both?

Sebastian
-
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

[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux