From: Mao Wenan <maowenan@huawei.com>
To: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<weiyongjun1@huawei.com>, <chenweilong@huawei.com>
Subject: [PATCH net-next] TLP: Don't reschedule PTO when there's one outstanding TLP retransmission.
Date: Tue, 25 Jul 2017 16:35:35 +0800 [thread overview]
Message-ID: <1500971735-21852-1-git-send-email-maowenan@huawei.com> (raw)
If there is one TLP probe went out(TLP use the write_queue_tail packet
as TLP probe, we assume this first TLP probe named A), and this TLP
probe was not acked by receive side.
Then the transmit side sent the next two packetes out(named B,C), but
unfortunately these two packets are also not acked by receive side.
And then there is one data packet with ack_seq A arrive, in tcp_ack()
will call tcp_schedule_loss_probe() to rearm PTO, the handler
tcp_send_loss_probe() pass if(tp->tlp_high_seq)(because there is
one outstanding TLP named A,tp->tlp_high_seq is not zero),
so the new TLP probe can't be went out and need to rearm the RTO
timer(timeout is relative to the transmit time of the write queue head).
After this, another data packet with ack_seq A is received,
if the tlp_time_stamp is after rto_time_stamp, it will reset the
TLP timeout with delta value, which is before previous RTO timeout,
so PTO is rearm and previous RTO is cleared. This TLP probe also can't
be sent out because of tp->tlp_high_seq != 0, so there is no way(or need
very long time)to retransmit the packet because of TLP A is lost.
This fix is not to pass the if(tp->tlp_high_seq) in tcp_schedule_loss_probe()
when TLP PTO is after RTO, It is no need to reschedule PTO when there
is one outstanding TLP retransmission, so if the TLP A is lost then RTO can
retransmit that packet, and tp->tlp_high_seq will be set to 0. After this TLP
will go to the normal work process.
Signed-off-by: Mao Wenan <maowenan@huawei.com>
---
net/ipv4/tcp_output.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 886d874..0c8da1c 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2423,6 +2423,10 @@ bool tcp_schedule_loss_probe(struct sock *sk)
tlp_time_stamp = tcp_jiffies32 + timeout;
rto_time_stamp = (u32)inet_csk(sk)->icsk_timeout;
if ((s32)(tlp_time_stamp - rto_time_stamp) > 0) {
+ /*It is no need to reschedule PTO when there is one outstanding TLP retransmission*/
+ if (tp->tlp_high_seq) {
+ return false;
+ }
s32 delta = rto_time_stamp - tcp_jiffies32;
if (delta > 0)
timeout = delta;
--
2.5.0
next reply other threads:[~2017-07-25 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 8:35 Mao Wenan [this message]
2017-07-25 9:19 ` [PATCH net-next] TLP: Don't reschedule PTO when there's one outstanding TLP retransmission maowenan
2017-07-25 9:54 ` Sergei Shtylyov
2017-07-26 1:26 ` maowenan
2017-07-25 13:29 ` Neal Cardwell
2017-07-26 2:12 ` maowenan
2017-07-26 16:45 ` Yuchung Cheng
2017-07-27 1:28 ` maowenan
2017-07-28 22:57 ` Neal Cardwell
2017-07-26 9:35 ` kbuild test robot
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=1500971735-21852-1-git-send-email-maowenan@huawei.com \
--to=maowenan@huawei.com \
--cc=chenweilong@huawei.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=weiyongjun1@huawei.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