Date: Tue, 21 Dec 1999 16:05:54 -0600 From: Jonathan Lemon <jlemon@flugsvamp.com> To: Matthew Dillon <dillon@apollo.backplane.com>, hackers@freebsd.org Subject: Re: Odd TCP glitches in new currents Message-ID: <19991221160554.A10150@prism.flugsvamp.com> In-Reply-To: <199912212146.PAA05052@free.pcs> References: <199912212146.PAA05052@free.pcs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Dec 1999 12:50:50 -0800 (PST), Matthew Dillon wrote: > What happens when you specify a 1-tick timeout and the tick interrupt > occurs a microsecond later? For that matter what happens when you want > 1.5 ticks worth of timeout? Do you get only 1? What happens is that > the TCP stack thinks it timed out when it only just sent the packet a > few microseconds ago. This should be taken care of by the TCP_REXMTVAL macro, it adds in one additional tick, plus .5 ticks for rounding. It's possible that I've defined the TCPTV_MIN value to be wrong, you could try bumping this up while I go back and review my notes. -- Jonaghan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991221160554.A10150>