Netdev List
 help / color / mirror / Atom feed
From: Nils Juenemann <nils.juenemann@gmail.com>
To: rjethwani@everpuredata.com
Cc: borisp@nvidia.com, davem@davemloft.net, edumazet@google.com,
	john.fastabend@gmail.com, kuba@kernel.org, leon@kernel.org,
	mbloch@nvidia.com, netdev@vger.kernel.org, pabeni@redhat.com,
	saeedm@nvidia.com, sd@queasysnail.net, tariqt@nvidia.com
Subject: Re: [PATCH net-next v14 0/9] tls: Add TLS 1.3 hardware offload support
Date: Tue,  7 Jul 2026 21:34:43 +0200	[thread overview]
Message-ID: <20260707193443.44553-1-nils.juenemann@gmail.com> (raw)
In-Reply-To: <CAKaoeS3Yg=kncNQRRcVh8JrQXy4Aah=3fuBwcitD6mjAEJOKOw@mail.gmail.com>

On Mon, Jul 6, 2026 at 3:14 PM Rishikesh Jethwani <rjethwani@everpuredata.com> wrote:
>
> Following two patches should fix this issue:
[...]

Thanks, Rishikesh.

Both patches apply cleanly on net-next and fix the crash in our setup. I
tested repeated channel-count changes between 64 and 32 under live TLS 1.3
RX HW offload load.

Tested-by: Nils Juenemann <nils.juenemann@gmail.com>

  reply	other threads:[~2026-07-07 19:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 21:27 [PATCH net-next v14 0/9] tls: Add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 1/9] net: tls: reject TLS 1.3 offload in chcr_ktls and nfp drivers Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 2/9] net/mlx5e: add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 3/9] tls: " Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 4/9] tls: split tls_set_sw_offload into init and finalize stages Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 5/9] tls: prep helpers and refactors for HW offload KeyUpdate Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 6/9] tls: device: add TX KeyUpdate support Rishikesh Jethwani
2026-05-25 21:16   ` Jakub Kicinski
2026-06-17 22:32     ` Rishikesh Jethwani
2026-06-17 22:56       ` Jakub Kicinski
2026-05-15 21:27 ` [PATCH v14 7/9] tls: device: add RX " Rishikesh Jethwani
2026-05-25 21:16   ` Jakub Kicinski
2026-06-17 22:36     ` Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 8/9] tls: device: add tracepoints for RX KeyUpdate path Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 9/9] selftests: net: add TLS hardware offload test Rishikesh Jethwani
2026-05-25 21:16   ` Jakub Kicinski
2026-05-17 22:21 ` [PATCH net-next v14 0/9] tls: Add TLS 1.3 hardware offload support Sabrina Dubroca
2026-06-27 21:06 ` Nils Juenemann
2026-07-06 22:14   ` Rishikesh Jethwani
2026-07-07 19:34     ` Nils Juenemann [this message]
2026-07-05 10:44 ` Nils Juenemann
2026-07-07 22:38   ` Rishikesh Jethwani
2026-07-07 23:23     ` Nils Juenemann
2026-07-08  0:02       ` Nils Juenemann
2026-07-08  0:31         ` Rishikesh Jethwani
2026-07-08  6:03           ` Nils Juenemann
2026-07-10 17:56             ` Rishikesh Jethwani

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=20260707193443.44553-1-nils.juenemann@gmail.com \
    --to=nils.juenemann@gmail.com \
    --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@everpuredata.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox