From owner-freebsd-current Tue Dec 21 14:16:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 8079514CC9 for ; Tue, 21 Dec 1999 14:16:25 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id QAA24894; Tue, 21 Dec 1999 16:16:23 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id QAA29278; Tue, 21 Dec 1999 16:16:21 -0600 (CST) Message-ID: <19991221161621.17529@right.PCS> Date: Tue, 21 Dec 1999 16:16:21 -0600 From: Jonathan Lemon To: Garrett Wollman Cc: Matthew Dillon , freebsd-current@freebsd.org Subject: Re: Odd TCP glitches in new currents References: <199912212050.MAA84567@apollo.backplane.com> <199912212100.QAA93975@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199912212100.QAA93975@khavrinen.lcs.mit.edu>; from Garrett Wollman on Dec 12, 1999 at 04:00:00PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 12, 1999 at 04:00:00PM -0500, Garrett Wollman wrote: > < 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