From: patchwork-bot+netdevbpf@kernel.org
To: Hechao Li <hli@netflix.com>
Cc: edumazet@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, soheil@google.com, netdev@vger.kernel.org,
tycho@tycho.pizza
Subject: Re: [PATCH net-next v3] tcp: increase the default TCP scaling ratio
Date: Fri, 12 Apr 2024 10:10:35 +0000 [thread overview]
Message-ID: <171291663506.22467.14336127401186077552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240409164355.1721078-1-hli@netflix.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 9 Apr 2024 09:43:55 -0700 you wrote:
> After commit dfa2f0483360 ("tcp: get rid of sysctl_tcp_adv_win_scale"),
> we noticed an application-level timeout due to reduced throughput.
>
> Before the commit, for a client that sets SO_RCVBUF to 65k, it takes
> around 22 seconds to transfer 10M data. After the commit, it takes 40
> seconds. Because our application has a 30-second timeout, this
> regression broke the application.
>
> [...]
Here is the summary with links:
- [net-next,v3] tcp: increase the default TCP scaling ratio
https://git.kernel.org/netdev/net-next/c/697a6c8cec03
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-04-12 10:10 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
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 [this message]
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=171291663506.22467.14336127401186077552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hli@netflix.com \
--cc=kuba@kernel.org \
--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).