diff options
author | Dave Watson <davejwatson@fb.com> | 2019-01-31 01:08:21 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-02-02 02:05:07 +0300 |
commit | 5b053e121ffdec851dc3a7046e9bece287a3c5b1 (patch) | |
tree | 1fb586291a821fe00e7524a61b94ffec5975d403 /include | |
parent | 665cf634e6d56b6864ec0e6d6c15fd5e6b8ad7e2 (diff) | |
download | linux-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 'include')
-rw-r--r-- | include/net/tls.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/net/tls.h b/include/net/tls.h index 004bf01ce868..a93a8ed8f716 100644 --- a/include/net/tls.h +++ b/include/net/tls.h @@ -142,6 +142,7 @@ struct tls_sw_context_tx { struct list_head tx_list; atomic_t encrypt_pending; int async_notify; + int async_capable; #define BIT_TX_SCHEDULED 0 unsigned long tx_bitmask; |