From: Meenakshi Aggarwal <meenakshi.aggarwal@xxxxxxx>
This series includes patches to remove CRYPTO_ALG_ALLOCATES_MEMORY flag
and allocate the required memory within the crypto request object.
CRYPTO_ALG_ALLOCATES_MEMORY flag is limited only to dm-crypt use-cases,
which seems to be 4 entries maximum.
Therefore in reqsize we allocate memory for maximum 4 entries
for src and 1 for IV, and the same for dst, both aligned.
If the driver needs more than the 4 entries maximum, the memory
is dynamically allocated, at runtime.
Meenakshi Aggarwal (5):
crypto:caam - avoid allocating memory at crypto request runtime for
skcipher
crypto:caam - avoid allocating memory at crypto request runtime for
aead
crypto: caam - avoid allocating memory at crypto request runtime for
hash
crypto: caam/qi - avoid allocating memory at crypto request runtime
crypto: caam/qi2 - avoid allocating memory at crypto request runtime
drivers/crypto/caam/caamalg.c | 138 +++++++---
drivers/crypto/caam/caamalg_qi.c | 131 +++++++---
drivers/crypto/caam/caamalg_qi2.c | 421 ++++++++++++++++++++----------
drivers/crypto/caam/caamalg_qi2.h | 6 +
drivers/crypto/caam/caamhash.c | 77 ++++--
5 files changed, 542 insertions(+), 231 deletions(-)
--
2.25.1
