From: patchwork-bot+netdevbpf@kernel.org
To: Pengcheng Yang <yangpc@wangsu.com>
Cc: edumazet@google.com, ncardwell@google.com, ycheng@google.com,
netdev@vger.kernel.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net] tcp: fix F-RTO may not work correctly when receiving DSACK
Date: Thu, 28 Apr 2022 17:40:11 +0000 [thread overview]
Message-ID: <165116761177.10854.18409623100154256898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1650967419-2150-1-git-send-email-yangpc@wangsu.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 Apr 2022 18:03:39 +0800 you wrote:
> Currently DSACK is regarded as a dupack, which may cause
> F-RTO to incorrectly enter "loss was real" when receiving
> DSACK.
>
> Packetdrill to demonstrate:
>
> // Enable F-RTO and TLP
> 0 `sysctl -q net.ipv4.tcp_frto=2`
> 0 `sysctl -q net.ipv4.tcp_early_retrans=3`
> 0 `sysctl -q net.ipv4.tcp_congestion_control=cubic`
>
> [...]
Here is the summary with links:
- [net] tcp: fix F-RTO may not work correctly when receiving DSACK
https://git.kernel.org/netdev/net/c/d9157f6806d1
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:[~2022-04-28 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 10:03 [PATCH net] tcp: fix F-RTO may not work correctly when receiving DSACK Pengcheng Yang
2022-04-28 17:06 ` Neal Cardwell
2022-04-28 17:11 ` Eric Dumazet
2022-04-28 17:40 ` 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=165116761177.10854.18409623100154256898.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangpc@wangsu.com \
--cc=ycheng@google.com \
--cc=yoshfuji@linux-ipv6.org \
/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).