From: Jakub Kicinski <kuba@kernel.org>
To: Hechao Li <hli@netflix.com>
Cc: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Soheil Hassas Yeganeh <soheil@google.com>,
netdev@vger.kernel.org, kernel-developers@netflix.com,
Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [PATCH net-next] tcp: update window_clamp together with scaling_ratio
Date: Wed, 3 Apr 2024 07:13:32 -0700 [thread overview]
Message-ID: <20240403071332.49c219e8@kernel.org> (raw)
In-Reply-To: <20240402215405.432863-1-hli@netflix.com>
On Tue, 2 Apr 2024 14:54:06 -0700 Hechao Li wrote:
> After commit dfa2f0483360 ("tcp: get rid of sysctl_tcp_adv_win_scale"),
> we noticed an application-level timeout due to reduced throughput. This
> can be reproduced by the following minimal client and server program.
Hi Hechao, nice to e-meet you :)
I suspect Eric may say that SO_RCVBUF = 64k is not very reasonable.
But I'll leave the technical review to him.
What I noticed is that our cryptic CI system appears to point at this
change as breaking BPF tests:
https://netdev.bots.linux.dev/flakes.html?min-flip=0&pw-n=0&tn-needle=gh-bpf
We accumulate all outstanding patches and test together.
BPF broke at net-next-2024-04-03--00-00, and:
$ cidiff origin/net-next-2024-04-02--21-00 \
origin/net-next-2024-04-03--00-00
+tcp: update window_clamp together with scaling_ratio
+tools: ynl: ethtool.py: Output timestamping statistics from tsinfo-get operation
+netlink: specs: ethtool: add header-flags enumeration
+net/mlx5e: Implement ethtool hardware timestamping statistics
+net/mlx5e: Introduce timestamps statistic counter for Tx DMA layer
+net/mlx5e: Introduce lost_cqe statistic counter for PTP Tx port timestamping CQ
+ethtool: add interface to read Tx hardware timestamping statistics
The other patches are all driver stuff..
Here's the BPF CI output:
https://github.com/kernel-patches/bpf/actions/runs/8538300303
next prev parent reply other threads:[~2024-04-03 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 21:54 [PATCH net-next] tcp: update window_clamp together with scaling_ratio Hechao Li
2024-04-03 14:13 ` Jakub Kicinski [this message]
2024-04-03 14:22 ` Eric Dumazet
2024-04-03 14:49 ` Eric Dumazet
2024-04-03 16:30 ` Hechao Li
2024-04-03 16:43 ` Eric Dumazet
2024-04-04 10:58 ` Eric Dumazet
2024-04-08 23:32 ` [PATCH net-next v2] tcp: increase the default TCP scaling ratio Hechao Li
2024-04-09 7:12 ` Eric Dumazet
2024-04-09 16:43 ` [PATCH net-next v3] " Hechao Li
2024-04-12 10:10 ` patchwork-bot+netdevbpf
2024-04-09 16:51 ` [PATCH net-next] tcp: update window_clamp together with scaling_ratio Neal Cardwell
2024-04-09 21:59 ` Hechao Li
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=20240403071332.49c219e8@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hli@netflix.com \
--cc=kernel-developers@netflix.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.com \
--cc=tycho@tycho.pizza \
/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).