[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200527.150726.628683182159628508.davem@davemloft.net>
Date: Wed, 27 May 2020 15:07:26 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: tariqt@...lanox.com
Cc: kuba@...nel.org, netdev@...r.kernel.org, borisp@...lanox.com,
maximmi@...lanox.com, saeedm@...lanox.com
Subject: Re: [PATCH net-next] net/tls: Add force_resync for driver resync
From: Tariq Toukan <tariqt@...lanox.com>
Date: Wed, 27 May 2020 12:25:26 +0300
> This patch adds a field to the tls rx offload context which enables
> drivers to force a send_resync call.
>
> This field can be used by drivers to request a resync at the next
> possible tls record. It is beneficial for hardware that provides the
> resync sequence number asynchronously. In such cases, the packet that
> triggered the resync does not contain the information required for a
> resync. Instead, the driver requests resync for all the following
> TLS record until the asynchronous notification with the resync request
> TCP sequence arrives.
>
> A following series for mlx5e ConnectX-6DX TLS RX offload support will
> use this mechanism.
>
> Signed-off-by: Boris Pismenny <borisp@...lanox.com>
> Signed-off-by: Tariq Toukan <tariqt@...lanox.com>
> Reviewed-by: Maxim Mikityanskiy <maximmi@...lanox.com>
> Reviewed-by: Saeed Mahameed <saeedm@...lanox.com>
Applied, thanks.
Powered by blists - more mailing lists