public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
	edumazet@google.com
Cc: netdev@vger.kernel.org, saeedm@nvidia.com, tariqt@nvidia.com,
	mbloch@nvidia.com, borisp@nvidia.com, john.fastabend@gmail.com,
	leon@kernel.org, Rishikesh Jethwani <rjethwani@purestorage.com>
Subject: Re: [PATCH v6 0/4] tls: Add TLS 1.3 hardware offload support
Date: Thu, 5 Feb 2026 00:42:41 +0100	[thread overview]
Message-ID: <aYPZcTAaRiLaCLQN@krikkit> (raw)
In-Reply-To: <20260203184835.3619101-1-rjethwani@purestorage.com>

2026-02-03, 11:48:31 -0700, Rishikesh Jethwani wrote:
> Hi all,
> 
> This patch series adds TLS 1.3 support to the kernel TLS hardware offload
> infrastructure, enabling hardware acceleration for TLS 1.3 connections
> including KeyUpdate (rekey) support. It also adds a selftest for
> validating hardware offload functionality.

@Maintainers Sorry, I haven't been able to look at this in detail yet,
could I get some more time?

-- 
Sabrina

  parent reply	other threads:[~2026-02-04 23:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 18:48 [PATCH v6 0/4] tls: Add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-02-03 18:48 ` [PATCH v6 1/4] tls: add " Rishikesh Jethwani
2026-02-03 18:48 ` [PATCH v6 2/4] tls: add hardware offload key update support Rishikesh Jethwani
2026-02-03 18:48 ` [PATCH v6 3/4] mlx5: TLS 1.3 hardware offload support Rishikesh Jethwani
2026-02-03 18:48 ` [PATCH v6 4/4] selftests: tls: add two-node hardware offload test Rishikesh Jethwani
2026-02-05  2:52   ` Jakub Kicinski
2026-02-04 23:42 ` Sabrina Dubroca [this message]
2026-02-05  2:49   ` [PATCH v6 0/4] 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=aYPZcTAaRiLaCLQN@krikkit \
    --to=sd@queasysnail.net \
    --cc=borisp@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox