On Tue, Jan 20, 2015 at 04:35:41AM +0100, Stephan Mueller wrote: > > This in turn would then turn the __driver implementation into a full GCM > implementation. That would mean that we should rename it from __driver > into gcm(aes) / gcm-aesni. No you shouldn't because it'll fail in interrupt context where you cannot use those special instructions. The whole point of this setup is to use accelerated instructions where possible, and otherwise fall back to a separate thread where we can do so safely. Cheers, -- 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
