From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Max Chernoff <git@maxchernoff.ca>
Subject: Re: [PATCH 4/8] tcp: Acknowledge everything if sending buffer is less than SNDBUF_BIG
Date: Fri, 5 Dec 2025 02:20:12 +0100 [thread overview]
Message-ID: <20251205022012.2acceb8e@elisabeth> (raw)
In-Reply-To: <aTIiZkqvwcsx0f1l@zatzit>
On Fri, 5 Dec 2025 11:08:06 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Thu, Dec 04, 2025 at 08:45:37AM +0100, Stefano Brivio wrote:
> > ...instead of checking if it's less than SNDBUF_SMALL, because this
> > isn't simply an optimisation to coalesce ACK segments: we rely on
> > having enough data at once from the sender to make the buffer grow
> > by means of TCP buffer size tuning implemented in the Linux kernel.
> >
> > Use SNDBUF_BIG: above that, we don't need auto-tuning (even though
> > it might happen). SNDBUF_SMALL is too... small.
>
> Do you have an idea of how often sndbuf exceeds SNDBUF_BIG? I'm
> wondering if by making this change we might have largely eliminated
> the first branch in practice.
Before this series, or after 6/8 in this series, it happens quite
often. It depends on the bandwidth * delay product of course, but at 1
Gbps and 20 ms RTT we get there in a couple of seconds.
Maybe 1 MiB would make more sense for typical conditions, but I'd defer
this to a more adaptive implementation of the whole thing. I think it
should also depend on the RTT, ideally.
>
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > ---
> > tcp.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tcp.c b/tcp.c
> > index e4c5a5b..fbf97a0 100644
> > --- a/tcp.c
> > +++ b/tcp.c
> > @@ -1079,7 +1079,7 @@ int tcp_update_seqack_wnd(const struct ctx *c, struct tcp_tap_conn *conn,
> > if (bytes_acked_cap && !force_seq &&
> > !CONN_IS_CLOSING(conn) &&
> > !(conn->flags & LOCAL) && !tcp_rtt_dst_low(conn) &&
> > - (unsigned)SNDBUF_GET(conn) >= SNDBUF_SMALL) {
> > + (unsigned)SNDBUF_GET(conn) >= SNDBUF_BIG) {
> > if (!tinfo) {
> > tinfo = &tinfo_new;
> > if (getsockopt(s, SOL_TCP, TCP_INFO, tinfo, &sl))
> > --
> > 2.43.0
--
Stefano
next prev parent reply other threads:[~2025-12-05 1:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 7:45 [PATCH 0/8] tcp: Fix throughput issues with non-local peers Stefano Brivio
2025-12-04 7:45 ` [PATCH 1/8] tcp: Limit advertised window to available, not total sending buffer size Stefano Brivio
2025-12-04 23:10 ` David Gibson
2025-12-04 7:45 ` [PATCH 2/8] tcp: Adaptive interval based on RTT for socket-side acknowledgement checks Stefano Brivio
2025-12-04 23:48 ` David Gibson
2025-12-05 1:20 ` Stefano Brivio
2025-12-05 2:49 ` David Gibson
2025-12-04 7:45 ` [PATCH 3/8] tcp: Don't clear ACK_TO_TAP_DUE if we're advertising a zero-sized window Stefano Brivio
2025-12-04 23:50 ` David Gibson
2025-12-04 7:45 ` [PATCH 4/8] tcp: Acknowledge everything if sending buffer is less than SNDBUF_BIG Stefano Brivio
2025-12-05 0:08 ` David Gibson
2025-12-05 1:20 ` Stefano Brivio [this message]
2025-12-05 2:50 ` David Gibson
2025-12-08 0:19 ` Stefano Brivio
2025-12-04 7:45 ` [PATCH 5/8] tcp: Don't limit window to less-than-MSS values, use zero instead Stefano Brivio
2025-12-05 0:35 ` David Gibson
2025-12-05 1:20 ` Stefano Brivio
2025-12-05 2:53 ` David Gibson
2025-12-04 7:45 ` [PATCH 6/8] tcp: Allow exceeding the available sending buffer size in window advertisements Stefano Brivio
2025-12-05 2:34 ` David Gibson
2025-12-08 0:20 ` Stefano Brivio
2025-12-04 7:45 ` [PATCH 7/8] tcp: Send a duplicate ACK also on complete sendmsg() failure Stefano Brivio
2025-12-05 2:35 ` David Gibson
2025-12-04 7:45 ` [PATCH 8/8] tcp: Skip redundant ACK on partial " Stefano Brivio
2025-12-05 2:36 ` David Gibson
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=20251205022012.2acceb8e@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=git@maxchernoff.ca \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).