From: Jakub Kicinski <kuba@kernel.org>
To: "Chuck Lever" <cel@kernel.org>
Cc: john.fastabend@gmail.com, "Sabrina Dubroca" <sd@queasysnail.net>,
netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
"Chuck Lever" <chuck.lever@oracle.com>,
"Hannes Reinecke" <hare@suse.de>,
"Alistair Francis" <alistair.francis@wdc.com>
Subject: Re: [PATCH net-next v6 0/6] TLS read_sock performance scalability
Date: Fri, 27 Mar 2026 17:26:07 -0700 [thread overview]
Message-ID: <20260327172607.1ae2bde9@kernel.org> (raw)
In-Reply-To: <722ffab1-f3d8-4309-afa0-482d64ae3a33@app.fastmail.com>
On Fri, 27 Mar 2026 09:35:09 -0400 Chuck Lever wrote:
> On Thu, Mar 26, 2026, at 8:54 PM, Jakub Kicinski wrote:
> > On Thu, 26 Mar 2026 09:50:45 -0400 Chuck Lever wrote:
> >> I'd like to encourage in-kernel kTLS consumers (i.e., NFS and
> >> NVMe/TCP) to coalesce on the use of read_sock. When I suggested
> >> this to Hannes, he reported a number of nagging performance
> >> scalability issues with read_sock. This series is an attempt to
> >> run these issues down and get them fixed before we convert the
> >> above sock_recvmsg consumers over to read_sock.
> >>
> >> Batch async decryption and its submit/deliver scaffolding were
> >> dropped from this series because async_capable is always false
> >> for TLS 1.3, which NFS and NVMe/TCP both require. Async crypto
> >> support for TLS 1.3 is a prerequisite for revisiting that work.
> >
> > Please repost the remaining 5 patches
>
> To make sure I understand your request, do you mean the TLS-related
> patches that are pre-requisites for Alistair's KeyUpdate series?
Oh, no, sorry, we merged patch 1 as a Fix and shipped it to Linus.
I meant to ask for you to fetch net-next, rebase and repost.
Patch 1 should "disappear" (unless I messed something up)
prev parent reply other threads:[~2026-03-28 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 13:50 [PATCH net-next v6 0/6] TLS read_sock performance scalability Chuck Lever
2026-03-26 13:50 ` [PATCH net-next v6 1/6] tls: Purge async_hold in tls_decrypt_async_wait() Chuck Lever
2026-03-26 13:50 ` [PATCH net-next v6 2/6] tls: Abort the connection on decrypt failure Chuck Lever
2026-03-26 13:50 ` [PATCH net-next v6 3/6] tls: Fix dangling skb pointer in tls_sw_read_sock() Chuck Lever
2026-03-26 13:50 ` [PATCH net-next v6 4/6] tls: Factor tls_strp_msg_release() from tls_strp_msg_done() Chuck Lever
2026-03-26 13:50 ` [PATCH net-next v6 5/6] tls: Suppress spurious saved_data_ready on all receive paths Chuck Lever
2026-03-26 13:50 ` [PATCH net-next v6 6/6] tls: Flush backlog before waiting for a new record Chuck Lever
2026-03-26 22:34 ` [PATCH net-next v6 0/6] TLS read_sock performance scalability patchwork-bot+netdevbpf
2026-03-27 0:54 ` Jakub Kicinski
2026-03-27 13:35 ` Chuck Lever
2026-03-28 0:26 ` Jakub Kicinski [this message]
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=20260327172607.1ae2bde9@kernel.org \
--to=kuba@kernel.org \
--cc=alistair.francis@wdc.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hare@suse.de \
--cc=john.fastabend@gmail.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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