From: Hannes Reinecke <hare@suse.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "kernel-tls-handshake@lists.linux.dev"
<kernel-tls-handshake@lists.linux.dev>
Subject: psock patch
Date: Fri, 10 Mar 2023 18:11:43 +0100 [thread overview]
Message-ID: <7e6a350f-e4b8-c245-83bf-a4ccca2f46bc@suse.de> (raw)
Hi Chuck,
for the previous accept()-based patch series you had a
patch 'net: Add distinct sk_psock field', claiming that it
was required to get kTLS and any other ULP using sk_user_data
to run.
What happened to it?
Is it still required?
Reason I'm asking is that I'm seeing odd stalls during encrypted traffic
(command timeouts etc), whereas the TLS connection itself seems
to be happy.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
next reply other threads:[~2023-03-10 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:11 Hannes Reinecke [this message]
2023-03-10 17:43 ` psock patch Chuck Lever III
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=7e6a350f-e4b8-c245-83bf-a4ccca2f46bc@suse.de \
--to=hare@suse.de \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
/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