From: Jakub Kicinski <kuba@kernel.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] net/tls: avoid TCP window full during ->read_sock()
Date: Fri, 4 Aug 2023 17:57:00 -0700 [thread overview]
Message-ID: <20230804175700.1f88604b@kernel.org> (raw)
In-Reply-To: <20230803100809.29864-1-hare@suse.de>
On Thu, 3 Aug 2023 12:08:09 +0200 Hannes Reinecke wrote:
> When flushing the backlog after decoding each record in ->read_sock()
> we may end up with really long records, causing a TCP window full as
> the TCP window would only be increased again after we process the
> record. So we should rather process the record first to allow the
> TCP window to be increased again before flushing the backlog.
> - released = tls_read_flush_backlog(sk, prot, rxm->full_len, to_decrypt,
> - decrypted, &flushed_at);
> skb = darg.skb;
> + /* TLS 1.3 may have updated the length by more than overhead */
> + rxm = strp_msg(skb);
> + tlm = tls_msg(skb);
> decrypted += rxm->full_len;
>
> tls_rx_rec_done(ctx);
> @@ -2280,6 +2275,12 @@ int tls_sw_read_sock(struct sock *sk, read_descriptor_t *desc,
> goto read_sock_requeue;
> }
> copied += used;
> + /*
> + * flush backlog after processing the TLS record, otherwise we might
> + * end up with really large records and triggering a TCP window full.
> + */
> + released = tls_read_flush_backlog(sk, prot, decrypted - copied, decrypted,
> + copied, &flushed_at);
I'm surprised moving the flushing out makes a difference.
rx_list should generally hold at most 1 skb (16kB) unless something
is PEEKing the data.
Looking at it closer I think the problem may be calling args to
tls_read_flush_backlog(). Since we don't know how much data
reader wants we can't sensibly evaluate the first condition,
so how would it work if instead of this patch we did:
- released = tls_read_flush_backlog(sk, prot, rxm->full_len, to_decrypt,
+ released = tls_read_flush_backlog(sk, prot, INT_MAX, 0,
decrypted, &flushed_at);
That would give us a flush every 128k of data (or every record if
inq is shorter than 16kB).
side note - I still prefer 80 char max lines, please. It seems to result
in prettier code ovarall as it forces people to think more about code
structure.
> if (used < rxm->full_len) {
> rxm->offset += used;
> rxm->full_len -= used;
--
pw-bot: cr
next prev parent reply other threads:[~2023-08-05 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 10:08 [PATCH] net/tls: avoid TCP window full during ->read_sock() Hannes Reinecke
2023-08-05 0:57 ` Jakub Kicinski [this message]
2023-08-07 7:08 ` 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=20230804175700.1f88604b@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).