On Monday 11 August 2003 07:22 pm, Hare, Matthew wrote: > I have two systems running SuSE Linux. System 1 is running SuSE 7.1 > with the 2.2.18 kernel. System 2 is running SuSE 7.3 with the > 2.4.17 kernel. Both systems are PC based (Pentium III, 512MB RAM). > > > When I open a TCP connection from System 1 I get a reported window > size (I use Ethereal to check window sizes) of 32k. When I do the > same with System 2 I get a reported window size of 5840bytes and > the window size increases as the rate of data being sent via TCP > increases. This is causing me problems, I need a fixed window size > of 32k on System 2 so that it matches System 1. > We've encountered similar behavior on a server running Red Hat 9 starting with the ~5k window size and publishing it is willing to increase it (forgot the exact name of the flags), problem is the clients are all w2k systems (for using Chariot as the performance analyzer), and they don't seem to be able to handle that kind of window size management, so we're always stuck with the original ~5k window size and the performance sucks. When using w2k on the same server, everything starts with 64k window, so the performance is great. Isn't there a way to ask the TCP/IP stack not to begin with small window size and then try to increase, but rather start with the largest windows size and then decrease ? Using jumbo frames and TSO doesn't seem to help a lot. -- | Shmulik Hen Advanced Network Services | | Israel Design Center, Jerusalem | | LAN Access Division, Platform Networking | | Intel Communications Group, Intel corp. | - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
