Date: Mon, 26 Nov 2001 14:28:29 +0300 From: "Serg V. Chemisov" <serg@sirena2000.ru> To: larse@ISI.EDU Cc: Jonathan Lemon <jlemon@flugsvamp.com>, net@freebsd.org Subject: Re: decreasing TIME_WAIT duration(T/TCP?) Message-ID: <3C02275C.E4C56BF@sirena2000.ru> References: <PLEAKFMAJKNOEPLJKGBLGEJGCAAA.larse@isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Lars Eggert wrote: > > > In article > > <local.mail.freebsd-net/3BFE4622.DA72E0D5@sirena2000.ru> you write: > > >Hello! > > > > > >It is important to me to have duration of TIME_WAIT state of TCP > > >connection as short time as possible. > > > > Tweak net.inet.tcp.msl, which specifies the 2MSL timeout. > > And know what you are doing, it's there for a reason. If you need to > dramatically change this value, I'd wager your system would benefit from a > design change. > > Lars > -- > Lars Eggert <larse@isi.edu> Information Sciences Institute > http://www.isi.edu/larse/ University of Southern California Alan Cox wrote: | | > Machine is web serwer with reather big traffic. Why there is | > so much connections in TIME_WAIT state ? | | | "2 mintues" may be how the Linux kernel does it, but it's not the way | TCP says it should be done. | | TIME_WAIT should last for 2*MSL (maximum segment lifetime). I know it's | hard to calculate MSL, and if you make up a hard-coded value it has to | be long enough for the slowest connections. It could be that FreeBSD | 4.0 does do this calculation. If we can calculate semi-accurate MSLs | for each connection, TIME_WAIT states would be minimized. | | Even over a slow Internet link, the MSL can't be much longer than 10 | seconds or so. By then a segment has either been TTL'd out, or is | lost. I don't buy "MSL == 1 minute" at all. How to turn on this calculation for 4.x ? Serg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C02275C.E4C56BF>