From: Jakub Kicinski <kuba@kernel.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: nvme-tls and TCP window full
Date: Tue, 18 Jul 2023 11:59:21 -0700 [thread overview]
Message-ID: <20230718115921.4de52fd6@kernel.org> (raw)
In-Reply-To: <a77cd4ee-fb4d-aa7e-f0b0-8795534f2acd@suse.de>
On Thu, 13 Jul 2023 12:16:13 +0200 Hannes Reinecke wrote:
> >> And my reading seems that the current in-kernel TLS implementation
> >> assumes TCP as the underlying transport anyway, so no harm done.
> >> Jakub?
> >
> > While it is correct that the assumption for tcp only, I think the
> > right thing to do would be to store the original read_sock and call
> > that...
>
> Ah, sure. Or that.
Yup, sorry for late reply, read_sock could also be replaced by BPF
or some other thing, even if it's always TCP "at the bottom".
next prev parent reply other threads:[~2023-07-18 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f10a9e4a-b545-429d-803e-c1d63a084afe@suse.de>
[not found] ` <49422387-5ea3-af84-3f94-076c94748fff@grimberg.me>
[not found] ` <ed5b22c6-d862-8706-fc2e-5306ed1eaad2@grimberg.me>
[not found] ` <a50ee71b-8ee9-7636-917d-694eb2a482b4@suse.de>
[not found] ` <6a9e0fbf-ca1a-aadd-e79a-c70ecd14bc28@grimberg.me>
2023-07-13 9:48 ` nvme-tls and TCP window full Hannes Reinecke
2023-07-13 10:11 ` Sagi Grimberg
2023-07-13 10:16 ` Hannes Reinecke
2023-07-18 18:59 ` Jakub Kicinski [this message]
2023-07-19 7:27 ` Hannes Reinecke
2023-07-19 11:54 ` Sagi Grimberg
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=20230718115921.4de52fd6@kernel.org \
--to=kuba@kernel.org \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=sagi@grimberg.me \
/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;
as well as URLs for NNTP newsgroup(s).