From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, Julian Anastasov <ja@ssi.bg>,
Yuchung Cheng <ycheng@google.com>,
netdev <netdev@vger.kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Larry Brakmo <brakmo@google.com>
Subject: Re: [PATCH v7 net-next 2/2] tcp: switch rtt estimations to usec resolution
Date: Wed, 26 Feb 2014 17:21:25 -0800 [thread overview]
Message-ID: <530E9315.5080606@hp.com> (raw)
In-Reply-To: <20140226170908.5f028c88@nehalam.linuxnetplumber.net>
On 02/26/2014 05:09 PM, Stephen Hemminger wrote:
> Since srtt is scaled by 8 and is 32 bits, This does reduce the maximum
> possible RTT to 8 minutes or so. Which is fine, just wanted it to be
> noted.
I have encountered some situations recently, admittedly very
pathological, where the RTT through a VPN connection was measured in
minutes. I don't think it got as high as 8 minutes, but it did get as
high as three or so. Also mentioned only for the record.
rick jones
next prev parent reply other threads:[~2014-02-27 1:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 6:38 [PATCH net-next] tcp: switch rtt estimations to usec resolution Eric Dumazet
2014-02-23 7:36 ` Julian Anastasov
2014-02-23 17:55 ` Eric Dumazet
2014-02-23 18:50 ` [PATCH v2 " Eric Dumazet
2014-02-23 19:19 ` Yuchung Cheng
2014-02-23 21:41 ` Eric Dumazet
2014-02-24 4:42 ` [PATCH v3 " Eric Dumazet
2014-02-24 17:58 ` Eric Dumazet
2014-02-24 18:24 ` [PATCH v4 " Eric Dumazet
2014-02-24 20:47 ` Julian Anastasov
2014-02-24 22:13 ` Eric Dumazet
2014-02-24 23:01 ` Julian Anastasov
2014-02-24 23:31 ` [PATCH v5 " Eric Dumazet
2014-02-24 23:51 ` Stephen Hemminger
2014-02-25 0:15 ` David Miller
2014-02-25 1:11 ` Eric Dumazet
2014-02-25 1:38 ` Eric Dumazet
2014-02-25 6:22 ` [PATCH v6 net-next 1/2] net: add skb_mstamp infrastructure Eric Dumazet
2014-02-25 9:51 ` David Laight
2014-02-25 12:21 ` Eric Dumazet
2014-02-26 20:02 ` David Miller
2014-02-26 20:29 ` Eric Dumazet
2014-02-26 22:02 ` [PATCH v7 " Eric Dumazet
2014-02-26 22:04 ` David Miller
2014-02-25 6:22 ` [PATCH v6 net-next 2/2] tcp: switch rtt estimations to usec resolution Eric Dumazet
2014-02-25 17:46 ` Neal Cardwell
2014-02-25 18:17 ` Eric Dumazet
2014-02-25 19:13 ` Neal Cardwell
2014-02-26 22:02 ` [PATCH v7 " Eric Dumazet
2014-02-26 22:04 ` David Miller
2014-02-27 1:09 ` Stephen Hemminger
2014-02-27 1:21 ` Rick Jones [this message]
2014-02-27 9:57 ` David Laight
2014-02-27 2:25 ` Eric Dumazet
2014-02-24 22:19 ` [PATCH v4 net-next] " Eric Dumazet
2014-02-28 5:20 ` [PATCH v2 " Andi Kleen
2014-02-28 6:14 ` Eric Dumazet
2014-02-28 13:31 ` Andi Kleen
2014-02-28 13:51 ` Eric Dumazet
2014-02-23 19:11 ` [PATCH " Julian Anastasov
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=530E9315.5080606@hp.com \
--to=rick.jones2@hp.com \
--cc=brakmo@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=ja@ssi.bg \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--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 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).