From: patchwork-bot+netdevbpf@kernel.org
To: Pengcheng Yang <yangpc@wangsu.com>
Cc: edumazet@google.com, ncardwell@google.com, ycheng@google.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net] tcp: fix TLP timer not set when CA_STATE changes from DISORDER to OPEN
Date: Mon, 25 Jan 2021 22:00:10 +0000 [thread overview]
Message-ID: <161161201046.13127.13513638342264536567.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1611464834-23030-1-git-send-email-yangpc@wangsu.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Sun, 24 Jan 2021 13:07:14 +0800 you wrote:
> Upon receiving a cumulative ACK that changes the congestion state from
> Disorder to Open, the TLP timer is not set. If the sender is app-limited,
> it can only wait for the RTO timer to expire and retransmit.
>
> The reason for this is that the TLP timer is set before the congestion
> state changes in tcp_ack(), so we delay the time point of calling
> tcp_set_xmit_timer() until after tcp_fastretrans_alert() returns and
> remove the FLAG_SET_XMIT_TIMER from ack_flag when the RACK reorder timer
> is set.
>
> [...]
Here is the summary with links:
- [v2,net] tcp: fix TLP timer not set when CA_STATE changes from DISORDER to OPEN
https://git.kernel.org/netdev/net/c/62d9f1a6945b
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-01-25 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 5:07 [PATCH v2 net] tcp: fix TLP timer not set when CA_STATE changes from DISORDER to OPEN Pengcheng Yang
2021-01-24 17:00 ` Yuchung Cheng
2021-01-24 18:26 ` Neal Cardwell
2021-01-25 22:00 ` 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=161161201046.13127.13513638342264536567.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=yangpc@wangsu.com \
--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 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).