Re: [PATCH 7/7] lib/lzo: separate lzo-rle from lzo

2018-12-02 Thread Herbert Xu
On Mon, Dec 03, 2018 at 11:40:19AM +0900, Sergey Senozhatsky wrote: > > I'm not in any position to ask you to do this; white-space clean ups > are not very popular (it's OK for staging tree; not so much otherwise). > So we better ask David and Herbert. I'm fine with white space cleanups. Thanks,

Re: [PATCH 7/7] lib/lzo: separate lzo-rle from lzo

2018-12-02 Thread Sergey Senozhatsky
On (11/30/18 10:45), Dave Rodgman wrote: > Looking a bit more closely, these structs are formatted fairly > inconsistently in the crypto directory. So, lzo-rle is consistent with > what lzo does... but various other files do it differently. > > I'm happy to submit a whitespace cleanup patch if p

Re: [RFC/RFT PATCH] crypto: arm64/chacha - optimize for arbitrary length inputs

2018-12-02 Thread Ard Biesheuvel
On Fri, 30 Nov 2018 at 21:38, Ard Biesheuvel wrote: > > Update the 4-way NEON ChaCha routine so it can handle input of any > length >64 bytes in its entirety, rather than having to call into > the 1-way routine and/or do memcpy()s via temp buffers to handle the > tail of a ChaCha invocation that i

Re: [PATCH v2 3/6] crypto: x86/chacha20 - limit the preemption-disabled section

2018-12-02 Thread Martin Willi
> To improve responsiveness, disable preemption for each step of the > walk (which is at most PAGE_SIZE) rather than for the entire > encryption/decryption operation. It seems that it is not that uncommon for IPsec to get small inputs scattered over multiple blocks. Doing FPU context saving for