From: Tariq Toukan <tariqt@nvidia.com>
To: Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
"John Fastabend" <john.fastabend@gmail.com>,
Sabrina Dubroca <sd@queasysnail.net>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Gal Pressman <gal@nvidia.com>, Boris Pismenny <borisp@nvidia.com>,
Shahar Shitrit <shshitrit@nvidia.com>
Subject: [PATCH net 0/3] tls: Introduce and use RX async resync request cancel function
Date: Wed, 10 Sep 2025 09:47:38 +0300 [thread overview]
Message-ID: <1757486861-542133-1-git-send-email-tariqt@nvidia.com> (raw)
Hi,
This series by Shahar introduces RX async resync request cancel function
in tls module, and uses it in mlx5e driver.
For a device-offloaded TLS RX connection, the TLS module increments
rcd_delta each time a new TLS record is received, tracking the distance
from the original resync request. In the meanwhile, the device is
queried and is expected to respond, asynchronously.
However, if the device response is delayed or fails (e.g due to unstable
connection and device getting out of tracking, hardware errors, resource
exhaustion etc.), the TLS module keeps logging and incrementing
rcd_delta, which can lead to a WARN() when rcd_delta exceeds the
threshold.
This series improves this code area by canceling the resync request when
spotting an issue with the device response.
Regards,
Tariq
Shahar Shitrit (3):
net: tls: Introduce RX async resync request cancel function
net: tls: Cancel RX async resync request on rdc_delta overflow
net/mlx5e: kTLS, cancel RX async resync request in error flows
.../mellanox/mlx5/core/en_accel/ktls_rx.c | 29 +++++++++++++++++--
.../mellanox/mlx5/core/en_accel/ktls_txrx.h | 4 +++
.../net/ethernet/mellanox/mlx5/core/en_rx.c | 4 +++
include/net/tls.h | 9 ++++++
net/tls/tls_device.c | 5 +++-
5 files changed, 47 insertions(+), 4 deletions(-)
base-commit: 78dd8ad62cad4f5af22afc842890d531312bbb8a
--
2.31.1
next reply other threads:[~2025-09-10 6:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 6:47 Tariq Toukan [this message]
2025-09-10 6:47 ` [PATCH net 1/3] net: tls: Introduce " Tariq Toukan
2025-09-10 6:47 ` [PATCH net 2/3] net: tls: Cancel RX async resync request on rdc_delta overflow Tariq Toukan
2025-09-12 15:14 ` Sabrina Dubroca
2025-09-22 7:16 ` Shahar Shitrit
2025-09-23 19:16 ` Sabrina Dubroca
2025-10-20 8:02 ` Shahar Shitrit
2025-09-14 18:53 ` Jakub Kicinski
2025-09-22 7:18 ` Shahar Shitrit
2025-09-22 15:54 ` Sabrina Dubroca
2025-09-28 6:35 ` Shahar Shitrit
2025-09-29 9:54 ` Sabrina Dubroca
2025-09-10 6:47 ` [PATCH net 3/3] net/mlx5e: kTLS, cancel RX async resync request in error flows Tariq Toukan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1757486861-542133-1-git-send-email-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=sd@queasysnail.net \
--cc=shshitrit@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®