From: Jakub Kicinski Date: Fri, 29 Jul 2022 04:50:57 +0000 (-0700) Subject: Merge branch 'mlx5e-use-tls-tx-pool-to-improve-connection-rate' X-Git-Tag: v6.6.17~6916^2~39 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=68be7b82e77f5ddf4a216f49fd965e74caf3f2e8;p=platform%2Fkernel%2Flinux-rpi.git Merge branch 'mlx5e-use-tls-tx-pool-to-improve-connection-rate' Tariq Toukan says: ==================== mlx5e use TLS TX pool to improve connection rate To offload encryption operations, the mlx5 device maintains state and keeps track of every kTLS device-offloaded connection. Two HW objects are used per TX context of a kTLS offloaded connection: a. Transport interface send (TIS) object, to reach the HW context. b. Data Encryption Key (DEK) to perform the crypto operations. These two objects are created and destroyed per TLS TX context, via FW commands. In total, 4 FW commands are issued per TLS TX context, which seriously limits the connection rate. In this series, we aim to save creation and destroy of TIS objects by recycling them. Upon recycling of a TIS, the HW still needs to be notified for the re-mapping between a TIS and a context. This is done by posting WQEs via an SQ, significantly faster API than the FW command interface. A pool is used for recycling. The pool dynamically interacts to the load and connection rate, growing and shrinking accordingly. Saving the TIS FW commands per context increases connection rate by ~42%, from 11.6K to 16.5K connections per sec. Connection rate is still limited by FW bottleneck due to the remaining per context FW commands (DEK create/destroy). This will soon be addressed in a followup series. By combining the two series, the FW bottleneck will be released, and a significantly higher (about 100K connections per sec) kTLS TX device-offloaded connection rate is reached. ==================== Link: https://lore.kernel.org/r/20220727094346.10540-1-tariqt@nvidia.com Signed-off-by: Jakub Kicinski --- 68be7b82e77f5ddf4a216f49fd965e74caf3f2e8