On Mon, Jan 05, 2015 at 09:51:35AM -0800, Tadeusz Struk wrote: > On 01/05/2015 02:06 AM, Herbert Xu wrote: > > > > It appears that the GCM aesni implementation does not support > > 192/256-bit keys. This is not allowed as accelerated drivers > > must support everything supported by the software implementation. > > > > Could we add 192/256-bit support to it please? If for some reason > > this cannot be done then at least implement a software fallback > > so that it continues to work. > Yes, you are right. I'll look into it. While you're at it, can you please run some speed tests to show that this is actually faster than the generic gcm on top of ctr-aes-aesni and ghash-clmulni? If it isn't any faster (it really shouldn't be as far as I can see) then we can just kill it. Thanks! -- Email: Herbert Xu <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
