Re: [PATCH v3 0/4] crypto: aesni - Use zero-copy for gcm(aes) buffers that are partially contiguous

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

 



On Wed, Jan 31, 2018 at 12:27:18PM -0800, Junaid Shahid wrote:
> Changes in v3:
> - Rebased on top of the latest linux-next
> Changes in v2:
> - Integrated https://patchwork.kernel.org/patch/10173981
> 
> Currently, the AESNI gcm(aes) implementation uses zero-copy only when the
> entire src and dest request buffers, including the AAD, the data and the
> Auth Tag are contiguous. This series enables the use of zero-copy even if the
> AAD and/or Auth Tag are in different buffers than the actual data, as long as
> each of them individually satisfies the zero-copy conditions (i.e. the entire
> buffer is either in low-mem or within a single high-mem page). Furthermore,
> it also enables the use of zero-copy even if only one of src and dest satisfies
> these conditions rather than only when both of them do.
> 
> Junaid Shahid (4):
>   crypto: aesni - Fix out-of-bounds access of the AAD buffer in AVX
>     gcm-aesni
>   crypto: aesni - Enable one-sided zero copy for gcm(aes) request
>     buffers
>   crypto: aesni - Directly use kmap_atomic instead of scatter_walk
>     object in gcm(aes)
>   crypto: aesni - Use zero-copy for gcm(aes) even if the
>     AAD/Data/AuthTag are separate
> 
>  arch/x86/crypto/aesni-intel_avx-x86_64.S | 154 +++++-----------
>  arch/x86/crypto/aesni-intel_glue.c       | 307 +++++++++++++++++++------------
>  2 files changed, 227 insertions(+), 234 deletions(-)

I think this conflicts with Dave Watson's work.  Could you rebase
this on top of his patches?

Thanks,
-- 
Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt



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

  Powered by Linux