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

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

 



On Thu, Oct 04, 2007 at 10:35:12AM +0200, Sebastian Siewior wrote:
>
> Two last questions:
> - What about the i386 assembly vs generic implementation? Do you prefer
>   the patch that I have send earlier (choose the assembly by default
>   making the generic optional) or do you want both of them loaded at
>   the same time.

I'd prefer both to be built by default so that if something
does go wrong we can ask people to check by using aes-generic.

> - What might be the best fallback strategy for the s390 + geode aes
>   driver? 

I've been trying to avoid this :)

Yes your proposal is definitely on the right track.

My original plan is to have a template like keylen(aes,16) that
only supports key length 16.  So perhaps you can take a look at
doing that or come up with a different solution.

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

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

  Powered by Linux