diff options
| author |   David S. Miller <davem@davemloft.net> | 2018-08-13 08:41:09 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-08-13 08:41:09 -0700 |
| commit | 8f78004442202b4ee28657513d78e6bb937e877c (patch) | |
| tree | 2388709906c2696baa252891f4845d8a680b8369 /net/ipv6 | |
| parent | Merge branch 'ip-faster-in-order-IP-fragments' (diff) | |
| parent | net/tls: Combined memory allocation for decryption request (diff) | |
| download | linux-dev-8f78004442202b4ee28657513d78e6bb937e877c.tar.xz linux-dev-8f78004442202b4ee28657513d78e6bb937e877c.zip | |
Merge branch 'net-tls-Combined-memory-allocation-for-decryption-request'
Vakul Garg says:
====================
net/tls: Combined memory allocation for decryption request
This patch does a combined memory allocation from heap for scatterlists,
aead_request, aad and iv for the tls record decryption path. In present
code, aead_request is allocated from heap, scatterlists on a conditional
basis are allocated on heap or on stack. This is inefficient as it may
requires multiple kmalloc/kfree.
The initialization vector passed in cryption request is allocated on
stack. This is a problem since the stack memory is not dma-able from
crypto accelerators.
Doing one combined memory allocation for each decryption request fixes
both the above issues. It also paves a way to be able to submit multiple
async decryption requests while the previous one is pending i.e. being
processed or queued.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions