summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/imx6q-sabresd.dts
diff options
context:
space:
mode:
authorBoris Pismenny <borisp@nvidia.com>2022-05-18 11:27:31 +0200
committerPaolo Abeni <pabeni@redhat.com>2022-05-19 12:14:11 +0200
commitc1318b39c7d36bd5139a9c71044ff2b2d3c6f9d8 (patch)
treeab03a38f64254b0a40bcf4a6d1faef188e5a6fa0 /arch/arm/boot/dts/imx6q-sabresd.dts
parentnfp: flower: support ct merging when mangle action exists (diff)
downloadlinux-c1318b39c7d36bd5139a9c71044ff2b2d3c6f9d8.tar.xz
linux-c1318b39c7d36bd5139a9c71044ff2b2d3c6f9d8.zip
tls: Add opt-in zerocopy mode of sendfile()
TLS device offload copies sendfile data to a bounce buffer before transmitting. It allows to maintain the valid MAC on TLS records when the file contents change and a part of TLS record has to be retransmitted on TCP level. In many common use cases (like serving static files over HTTPS) the file contents are not changed on the fly. In many use cases breaking the connection is totally acceptable if the file is changed during transmission, because it would be received corrupted in any case. This commit allows to optimize performance for such use cases to providing a new optional mode of TLS sendfile(), in which the extra copy is skipped. Removing this copy improves performance significantly, as TLS and TCP sendfile perform the same operations, and the only overhead is TLS header/trailer insertion. The new mode can only be enabled with the new socket option named TLS_TX_ZEROCOPY_SENDFILE on per-socket basis. It preserves backwards compatibility with existing applications that rely on the copying behavior. The new mode is safe, meaning that unsolicited modifications of the file being sent can't break integrity of the kernel. The worst thing that can happen is sending a corrupted TLS record, which is in any case not forbidden when using regular TCP sockets. Sockets other than TLS device offload are not affected by the new socket option. The actual status of zerocopy sendfile can be queried with sock_diag. Performance numbers in a single-core test with 24 HTTPS streams on nginx, under 100% CPU load: * non-zerocopy: 33.6 Gbit/s * zerocopy: 79.92 Gbit/s CPU: Intel(R) Xeon(R) Platinum 8380 CPU @ 2.30GHz Signed-off-by: Boris Pismenny <borisp@nvidia.com> Signed-off-by: Tariq Toukan <tariqt@nvidia.com> Signed-off-by: Maxim Mikityanskiy <maximmi@nvidia.com> Reviewed-by: Jakub Kicinski <kuba@kernel.org> Link: https://lore.kernel.org/r/20220518092731.1243494-1-maximmi@nvidia.com Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'arch/arm/boot/dts/imx6q-sabresd.dts')
0 files changed, 0 insertions, 0 deletions