From: Jakub Kicinski <kuba@kernel.org>
To: Rishikesh Jethwani <rjethwani@purestorage.com>
Cc: netdev@vger.kernel.org, saeedm@nvidia.com, tariqt@nvidia.com,
mbloch@nvidia.com, borisp@nvidia.com, john.fastabend@gmail.com,
sd@queasysnail.net, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, leon@kernel.org
Subject: Re: [PATCH v5 0/3] tls: Add TLS 1.3 hardware offload support
Date: Thu, 22 Jan 2026 17:48:21 -0800 [thread overview]
Message-ID: <20260122174821.70553ffc@kernel.org> (raw)
In-Reply-To: <20260122192851.86670-1-rjethwani@purestorage.com>
On Thu, 22 Jan 2026 12:28:48 -0700 Rishikesh Jethwani wrote:
> - Rekey handling: HW offload key update (rekey) is not yet supported.
Not sure this series will be merged without rekeying.
We'll need to discuss pros and cons.
> Testing
> =======
> Tested on Mellanox ConnectX-6 Dx (Crypto Enabled).
>
> Both TX and RX hardware offload verified working with:
> - TLS 1.3 AES-GCM-128
> - TLS 1.3 AES-GCM-256
> - Multiple KeyUpdate cycles (rekey)
>
> Test methodology: ktls_test : https://github.com/insanum/ktls_test/tree/master
>
> Please review and provide feedback.
Selftests are a hard requirement, I already shared a link with more
info with you.
--
pw-bot: cr
next prev parent reply other threads:[~2026-01-23 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 19:28 [PATCH v5 0/3] tls: Add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-01-22 19:28 ` [PATCH v5 1/3] tls: add " Rishikesh Jethwani
2026-01-22 19:28 ` [PATCH v5 2/3] tls: add hardware offload key update support Rishikesh Jethwani
2026-01-22 19:28 ` [PATCH v5 3/3] mlx5: TLS 1.3 hardware offload support Rishikesh Jethwani
2026-01-23 1:48 ` Jakub Kicinski [this message]
2026-01-23 19:03 ` [PATCH v5 0/3] tls: Add " Rishikesh Jethwani
2026-01-26 22:07 ` Rishikesh Jethwani
2026-01-27 0:16 ` Jakub Kicinski
2026-02-03 18:55 ` Rishikesh Jethwani
2026-02-03 22:42 ` Jakub Kicinski
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=20260122174821.70553ffc@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=leon@kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rjethwani@purestorage.com \
--cc=saeedm@nvidia.com \
--cc=sd@queasysnail.net \
--cc=tariqt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.