[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180806163810.30880-1-vakul.garg@nxp.com>
Date: Mon, 6 Aug 2018 22:08:09 +0530
From: Vakul Garg <vakul.garg@....com>
To: netdev@...r.kernel.org
Cc: borisp@...lanox.com, aviadye@...lanox.com, davejwatson@...com,
davem@...emloft.net, Vakul Garg <vakul.garg@....com>
Subject: [PATCH RFC net-next 0/1] 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.
This patch has been built over Doron Roberts-Kedes's patch:
"net/tls: Calculate nsg for zerocopy path without skb_cow_data"
Vakul Garg (1):
net/tls: Combined memory allocation for decryption request
include/net/tls.h | 4 -
net/tls/tls_sw.c | 256 +++++++++++++++++++++++++++++++-----------------------
2 files changed, 147 insertions(+), 113 deletions(-)
--
2.13.6
Powered by blists - more mailing lists