summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorDave Watson <davejwatson@fb.com>2019-01-31 01:08:21 +0300
committerDavid S. Miller <davem@davemloft.net>2019-02-02 02:05:07 +0300
commit5b053e121ffdec851dc3a7046e9bece287a3c5b1 (patch)
tree1fb586291a821fe00e7524a61b94ffec5975d403 /crypto
parent665cf634e6d56b6864ec0e6d6c15fd5e6b8ad7e2 (diff)
downloadlinux-5b053e121ffdec851dc3a7046e9bece287a3c5b1.tar.xz
net: tls: Set async_capable for tls zerocopy only if we see EINPROGRESS
Currently we don't zerocopy if the crypto framework async bit is set. However some crypto algorithms (such as x86 AESNI) support async, but in the context of sendmsg, will never run asynchronously. Instead, check for actual EINPROGRESS return code before assuming algorithm is async. Signed-off-by: Dave Watson <davejwatson@fb.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions