From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
edumazet@google.com, ncardwell@google.com,
stephen@networkplumber.org, ycheng@google.com, soheil@google.com
Subject: Re: [PATCH net] tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited flows
Date: Thu, 25 Nov 2021 01:30:08 +0000 [thread overview]
Message-ID: <163780380877.5226.16376864840352024866.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211123202535.1843771-1-eric.dumazet@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 23 Nov 2021 12:25:35 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> While testing BIG TCP patch series, I was expecting that TCP_RR workloads
> with 80KB requests/answers would send one 80KB TSO packet,
> then being received as a single GRO packet.
>
> It turns out this was not happening, and the root cause was that
> cubic Hystart ACK train was triggering after a few (2 or 3) rounds of RPC.
>
> [...]
Here is the summary with links:
- [net] tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited flows
https://git.kernel.org/netdev/net/c/4e1fddc98d25
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-11-25 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 20:25 [PATCH net] tcp_cubic: fix spurious Hystart ACK train detections for not-cwnd-limited flows Eric Dumazet
2021-11-25 1:30 ` patchwork-bot+netdevbpf [this message]
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=163780380877.5226.16376864840352024866.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=soheil@google.com \
--cc=stephen@networkplumber.org \
--cc=ycheng@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.