This feature is supported on ConnectX-6 Dx crypto cards only.
Transport Layer Security (TLS) is a widely-deployed protocol used for securing TCP connections on the Internet. TLS is also a required feature for HTTP/2, the latest web standard. Kernel implementation of TLS (kTLS) provides new opportunities for offloading the protocol into the hardware.
TLS data-path offload allows the NIC to accelerate encryption, decryption and authentication of AES-GCM. TLS offload handles data as it goes through the device without storing any data, but only updating context. If the packet cannot be encrypted/decrypted by the device, then a software fallback handles the packet.
To avoid unnecessary complexity in the kernel, the TLS handshake is kept in the user space. A full TLS connection using the socket is done using the following scheme:
accept()on a standard TCP file descriptor.
setsockoptfunction on the kTLS file descriptor (FD) to pass them to the kernel.
splice()system calls on the KTLS FD.
Drivers can offer Tx and Rx packet encryption/decryption offload from the kernel into the NIC hardware. Upon receipt of a non-data TLS message (a control message), the kTLS socket returns an error, and the message is left on the original TCP socket instead. The kTLS socket is automatically unattached. Transfer of control back to the original encrypted FD is done by calling
getsockopt to receive the current sequence numbers, and inserting them into the TLS library.
For support in the kernel, make sure the following flags are set as follows.
For kTLS offloads with MLNX_EN drivers, kernel TLS module (kernel/net/tls) must be aligned to kernel.org 5.3 or later.
To enable kTLS Tx offload, run:
ethtool -K <ifs> tls-hw-tx-offload on
o enable kTLS Rx offload, run:
ethtool -K <ifs> tls-hw-rx-offload on
For further information on TLS offloads, please visit the following kernel documentation: