Re: [PATCH 00/10] crypto: x86_64 - Add SSE/AVX2 ChaCha20/Poly1305 ciphers

2015-07-11 Thread Martin Willi
If you're going to use sec you need to use at least 10 in order for it to be meaningful as shorter values often result in bogus numbers. Ok, I'll use sec=10 in v2. There is no fundamental difference compared to sec=1 (except for very short blocks): testing speed of

Re: [PATCH 0/14] crypto: aead - Phase oute seqniv

2015-07-11 Thread Herbert Xu
On Fri, Jul 10, 2015 at 07:57:11PM +0200, Stephan Mueller wrote: Am Freitag, 10. Juli 2015, 21:39:22 schrieb Herbert Xu: Hi Herbert, On Thu, Jul 09, 2015 at 01:38:07PM +0200, Stephan Mueller wrote: Actually, I found a problem that I have overlooked initally: rfc4106-gcm-aesni causes a

Re: [PATCH 0/14] crypto: aead - Phase oute seqniv

2015-07-11 Thread Herbert Xu
On Fri, Jul 10, 2015 at 08:46:00PM +0200, Stephan Mueller wrote: Am Freitag, 10. Juli 2015, 21:38:02 schrieb Herbert Xu: Hi Herbert, On Thu, Jul 09, 2015 at 12:19:53PM +0200, Stephan Mueller wrote: All GCM implementations available on recent Intel systems successfully tested (i.e NX and

Re: [PATCH v2 6/7] crypto: omap-aes: Add support for GCM mode

2015-07-11 Thread Herbert Xu
On Fri, Jul 10, 2015 at 07:39:35PM +0530, Lokesh Vutla wrote: If you don't mind can you elaborate more on the usage of rctx and ctx in the driver? The ctx is a property of the tfm and it's shared by all users of that tfm. So it must not be written to unless you use locking. The reqeust