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 net-next v11 0/6] tls: Add TLS 1.3 hardware offload support
Date: Tue, 31 Mar 2026 15:58:59 -0700 [thread overview]
Message-ID: <20260331155859.1f34ef38@kernel.org> (raw)
In-Reply-To: <20260331163757.149343-1-rjethwani@purestorage.com>
On Tue, 31 Mar 2026 10:37:51 -0600 Rishikesh Jethwani wrote:
> Changes in v11:
> - tls_device_complete_rekey(): flush pending open_rec (from MSG_MORE)
> via tls_sw_push_pending_record() before switching back to HW offload.
> Without this, data in an open SW record would be silently lost when
> the AEAD cipher is freed.
> - Selftest: enforce MIN_BUF_SIZE (16 bytes) on both client and server
> receive buffers to prevent KeyUpdate handshake message truncation
> with small -b values.
Not more than 1 version in a 24h period, please. No matter how trivial
the reason.
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
--
pv-bot: 24h
next prev parent reply other threads:[~2026-03-31 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 16:37 [PATCH net-next v11 0/6] tls: Add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-03-31 16:37 ` [PATCH v11 1/6] net: tls: reject TLS 1.3 offload in chcr_ktls and nfp drivers Rishikesh Jethwani
2026-03-31 16:37 ` [PATCH v11 2/6] net/mlx5e: add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-03-31 16:37 ` [PATCH v11 3/6] tls: " Rishikesh Jethwani
2026-03-31 16:37 ` [PATCH v11 4/6] tls: split tls_set_sw_offload into init and finalize stages Rishikesh Jethwani
2026-03-31 16:37 ` [PATCH v11 5/6] tls: add hardware offload key update support Rishikesh Jethwani
2026-03-31 16:37 ` [PATCH v11 6/6] selftests: net: add TLS hardware offload test Rishikesh Jethwani
2026-04-02 16:21 ` Sabrina Dubroca
2026-03-31 22:58 ` Jakub Kicinski [this message]
2026-04-02 3:16 ` [PATCH net-next v11 0/6] tls: Add TLS 1.3 hardware offload support 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=20260331155859.1f34ef38@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.