Messages in this thread | | | Date | Thu, 12 Dec 2002 22:26:55 -0800 | From | Nivedita Singhvi <> | Subject | Re: R: Kernel bug handling TCP_RTO_MAX? |
| |
Nivedita Singhvi wrote:
> our default init rto is 300, so currently we're going to timeout > on anything thats a 100ms over the min of 200. that is far > less conservative than setting an rto of 200 when your round > trip time is a thousand or 10,000 times less..does that make sense?
Doh! init rto is NOT 300ms, its 3 seconds. That minor blooper shreds my comparison argument a tad :)..but Dave's point renders that moot, in any case..
"David S. Miller" wrote:
> Actually, TCP_RTO_MIN cannot be made any smaller without > some serious thought. > > The reason it is 200ms is due to the granularity of the BSD > TCP socket timers. > > In short, the repercussions are not exactly well known, so it's > a research problem to fiddle here.
Ack.
Sometime in the not too distant future, the next generation of infrastructure will require this to be reworked :).
thanks, Nivedita - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |