Date: Thu, 18 Jul 2002 00:39:38 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: cvs-committers@FreeBSD.ORG, <cvs-all@FreeBSD.ORG> Subject: Re: cvs commit: src/sys/netinet tcp_timer.h Message-ID: <20020718001924.J83856-100000@patrocles.silby.com> In-Reply-To: <200207180445.g6I4jkD4006497@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Jul 2002, Matthew Dillon wrote: > Ok, how about this: > > #define TCPTV_MIN ( hz / 50 <= 3 ? 3 : hz / 50 ) /* minimum allowable value */ > > 20 milliseconds or 3 ticks, whichever is greater. The idea > being that 20 ms compensates for operating system variability > and/or polling issues. > > -Matt I'm starting to warm up to it, though a little higher would be nice. What's really bugging me is the subsequent retransmissions... perhaps we could constrain them such that the second or third had lower bounds as well? I still think retransmissions at: 30 60 120 240 480 would be bad, but maybe: 30 530 1530 (doubling from there) wouldn't be so bad. If you did that, then you wouldn't have to worry about significantly shortening the overall retranmission timeout period, or worry about repeatedly retransmitting before the link has time to recover from whatever caused the original and the first retransmission to be lost. Is that making any sense? I should probably get some sleep before I comment more. :) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020718001924.J83856-100000>