From owner-freebsd-current Tue Dec 21 13: 0:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5056915511; Tue, 21 Dec 1999 13:00:12 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA93975; Tue, 21 Dec 1999 16:00:00 -0500 (EST) (envelope-from wollman) Date: Tue, 21 Dec 1999 16:00:00 -0500 (EST) From: Garrett Wollman Message-Id: <199912212100.QAA93975@khavrinen.lcs.mit.edu> To: Matthew Dillon Cc: jlemon@freebsd.org, Subject: Odd TCP glitches in new currents In-Reply-To: <199912212050.MAA84567@apollo.backplane.com> References: <199912212050.MAA84567@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < 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. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message