netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: ian.mcdonald@jandi.co.nz, netdev@vger.kernel.org
Subject: Re: [PATCH] make _minimum_ TCP retransmission timeout configurable
Date: Wed, 29 Aug 2007 16:06:27 -0700	[thread overview]
Message-ID: <46D5FBF3.5050700@hp.com> (raw)
In-Reply-To: <20070829.153503.18295527.davem@davemloft.net>


> All of this seems to suggest that the RTO calculation is wrong.

That is a possiblity.  Or at least could be enhanced.

> It seems that packets in this network can be delayed several orders of
> magnitude longer than the usual round trip as measured by TCP.
> 
> What exactly causes such a huge delay?  What is the TCP measured RTO
> in these circumstances where spurious RTOs happen and a 3 second
> minimum RTO makes things better?

I belive the biggest component comes from link-layer retransmissions. 
There can also be some short outtages thanks to signal blocking, 
tunnels, people with big hats and whatnot that the link-layer 
retransmissions are trying to address.  The three seconds seems to be a 
value that gives the certainty that 99 times out of 10 the segment was 
indeed lost.

The trace I've been sent shows clean RTTs ranging from ~200 milliseconds 
to ~7000 milliseconds.

rick


  parent reply	other threads:[~2007-08-29 23:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 20:52 [PATCH] make _minimum_ TCP retransmission timeout configurable Rick Jones
2007-08-29 21:13 ` Eric Dumazet
2007-08-29 22:11   ` Rick Jones
2007-08-29 21:32 ` Ian McDonald
2007-08-29 21:46   ` David Miller
2007-08-29 22:10     ` Ian McDonald
2007-08-29 22:23       ` David Miller
2007-08-29 22:13     ` Stephen Hemminger
2007-08-29 22:28       ` David Miller
2007-08-29 22:51         ` Stephen Hemminger
2007-08-29 22:58           ` NCR, was " John Heffner
2007-08-29 22:59             ` David Miller
2007-08-29 22:32       ` Rick Jones
2007-08-29 22:29     ` Rick Jones
2007-08-29 22:35       ` David Miller
2007-08-29 22:48         ` John Heffner
2007-08-29 22:52           ` John Heffner
2007-08-29 22:53         ` Edgar E. Iglesias
2007-08-29 23:06         ` Rick Jones [this message]
2007-08-29 23:15           ` David Miller
2007-08-29 23:31             ` Rick Jones
2007-08-30  5:22               ` Krishna Kumar2
2007-08-30 17:10                 ` Rick Jones
2007-08-29 23:44             ` John Heffner
2007-09-05 19:04             ` Ilpo Järvinen
2007-09-06 20:39               ` David Miller
2007-08-29 22:09   ` Rick Jones
2007-08-29 22:20     ` David Miller
2007-08-29 22:33       ` Ian McDonald
2007-08-29 22:37         ` David Miller

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=46D5FBF3.5050700@hp.com \
    --to=rick.jones2@hp.com \
    --cc=davem@davemloft.net \
    --cc=ian.mcdonald@jandi.co.nz \
    --cc=netdev@vger.kernel.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).