From owner-freebsd-current Tue Dec 21 13:14:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 15999154D9; Tue, 21 Dec 1999 13:14:12 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA16591; Tue, 21 Dec 1999 22:13:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: Matthew Dillon , jlemon@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Odd TCP glitches in new currents In-reply-to: Your message of "Tue, 21 Dec 1999 16:00:00 EST." <199912212100.QAA93975@khavrinen.lcs.mit.edu> Date: Tue, 21 Dec 1999 22:13:51 +0100 Message-ID: <16589.945810831@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912212100.QAA93975@khavrinen.lcs.mit.edu>, Garrett Wollman write s: >< 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. I assume you mean 20 msec (= 2 tick @ 100 Hz ) ? 200 msec is enough to get halfway around the globe... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message