Date: Tue, 21 Dec 1999 22:13:51 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: Matthew Dillon <dillon@apollo.backplane.com>, jlemon@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Odd TCP glitches in new currents Message-ID: <16589.945810831@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 21 Dec 1999 16:00:00 EST." <199912212100.QAA93975@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199912212100.QAA93975@khavrinen.lcs.mit.edu>, Garrett Wollman write s: ><<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. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16589.945810831>