Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Dec 1999 16:16:21 -0600
From:      Jonathan Lemon <jlemon@americantv.com>
To:        Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc:        Matthew Dillon <dillon@apollo.backplane.com>, freebsd-current@freebsd.org
Subject:   Re: Odd TCP glitches in new currents
Message-ID:  <19991221161621.17529@right.PCS>
In-Reply-To: <199912212100.QAA93975@khavrinen.lcs.mit.edu>; from Garrett Wollman on Dec 12, 1999 at 04:00:00PM -0500
References:  <199912212050.MAA84567@apollo.backplane.com> <199912212100.QAA93975@khavrinen.lcs.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 12, 1999 at 04:00:00PM -0500, Garrett Wollman wrote:
> <<On Tue, 21 Dec 1999 12:50:50 -0800 (PST), Matthew Dillon <dillon@apollo.backplane.com> said:
> 
> >     I have NOT tested this fix yet, so I don't know if it works, but I
> >     believe the problem is that on high speed networks the milliscond round
> >     trip delay is short enough that you can get 1-tick timeouts.
> 
> Hmmm.  I thought we agreed that 200 msec was the minimum reasonable
> RTO.  That code doesn't seem to have made it in.


Yes, I remember having that discussion, but can't seem to find any
corresponding code.  I thought I put in a sysctl for changing 
TCPTV_MIN, but perhaps I took it out after putting in the bad-
retransmit recovery section.
--
Jonathan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991221161621.17529>