From: Ido Yariv <ido@wizery.com>
To: "David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
Nandita Dukkipati <nanditad@google.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ido Yariv <ido@wizery.com>, Ido Yariv <idox.yariv@intel.com>
Subject: [PATCH] net: tcp: Fix a PTO timing granularity issue
Date: Tue, 26 May 2015 10:25:58 -0400 [thread overview]
Message-ID: <1432650358-11470-1-git-send-email-ido@wizery.com> (raw)
The Tail Loss Probe RFC specifies that the PTO value should be set to
max(2 * SRTT, 10ms), where SRTT is the smoothed round-trip time.
The PTO value is converted to jiffies, so the timer might expire
prematurely. This is especially problematic on systems in which HZ=100.
To work around this issue, increase the number of jiffies by one,
ensuring that the timeout won't expire in less than 10ms.
Signed-off-by: Ido Yariv <idox.yariv@intel.com>
---
net/ipv4/tcp_output.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 534e5fd..6f57d3d 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2207,7 +2207,7 @@ bool tcp_schedule_loss_probe(struct sock *sk)
if (tp->packets_out == 1)
timeout = max_t(u32, timeout,
(rtt + (rtt >> 1) + TCP_DELACK_MAX));
- timeout = max_t(u32, timeout, msecs_to_jiffies(10));
+ timeout = max_t(u32, timeout, msecs_to_jiffies(10) + 1);
/* If RTO is shorter, just schedule TLP in its place. */
tlp_time_stamp = tcp_time_stamp + timeout;
--
2.1.0
next reply other threads:[~2015-05-26 14:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 14:25 Ido Yariv [this message]
2015-05-26 16:23 ` [PATCH] net: tcp: Fix a PTO timing granularity issue Eric Dumazet
2015-05-26 17:02 ` Ido Yariv
2015-05-26 17:13 ` Eric Dumazet
2015-05-26 17:55 ` Ido Yariv
2015-05-26 18:13 ` Eric Dumazet
2015-05-26 20:17 ` Ido Yariv
2015-05-27 11:36 ` David Laight
2015-05-27 13:41 ` Eric Dumazet
2015-05-27 14:40 ` Ido Yariv
2015-05-27 14:56 ` Eric Dumazet
2015-05-27 15:23 ` Ido Yariv
2015-05-27 16:23 ` Eric Dumazet
2015-05-27 16:54 ` Ido Yariv
2015-05-27 17:24 ` Eric Dumazet
2015-05-27 19:15 ` Ido Yariv
2015-05-28 4:37 ` Ido Yariv
2015-05-28 8:55 ` David Laight
2015-05-28 12:33 ` [PATCH v6] " Ido Yariv
2015-05-26 18:25 ` [PATCH] " Eric Dumazet
2015-05-26 19:39 ` Ido Yariv
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=1432650358-11470-1-git-send-email-ido@wizery.com \
--to=ido@wizery.com \
--cc=davem@davemloft.net \
--cc=idox.yariv@intel.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=nanditad@google.com \
--cc=netdev@vger.kernel.org \
--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).