Subject: Dynamically setting the TCP window is hard ?
Message-ID: <1992Sep2.211354.24018@ugle.unit.no>
Keywords: TCP window
Sender: news@ugle.unit.no (NetNews Administrator)
Organization: SINTEF, Trondheim, Norway.
Date: Wed, 2 Sep 92 21:13:54 GMT
Lines: 37
Hello,
I want to set the TCP window selectively for high performance sessions on a high
bandwith*delay network.
I have tried to set the max windowsize for TCP on BSD-type systems with the
setsockopt( SO_RCVBUF ). That means setting the TCP internal receive buffer. By
this TCP hopefully will announce its entire buffer to the peer TCP. This works
well with SunOs 4.1.1/2, Cray/Unicos v6.013 and HP/UX systems, but DECstation
5000 Ultrix v4.2 does not announce a higher window than 32K on the initial SYN
response on a TCP connection setup even if the buffersize is confirmed to be set
higher by getsockopt.
What is the actual mechanism for TCP to determine max inital receive window
size and for me to influence it ?
Common to all systems above except Unicos is that they does not accept a higher
buffersize than about 50K - why is that ?
I guess that you can generate a kernel with fixed TCP buffersize larger than
50K. Then all TCP session for that system would have let say 64K window. Would that be more harmful to slow speed, normal delay , 64Kbps, networks than a 4K window ?
Regards
Olav
--
Olav Kvittem : SINTEF
RFC Address Olav.Kvittem@delab.sintef.no
OR Address C=no;ADMD=" ";PRMD=uninett;
O=sintef;OU=delab;S=Kvittem;G=Olav
Postal Address SINTEF DELAB
N-7034 Trondheim
Phone +47-7-532586(FAX)
Phone +47-7-596981
Description Research Scientist - Communication Networks