Greetings, Hardware: P4/2.8Ghz/1GB/40GB HDD/G4 FX5200 Intel 865PERL 1) When I boot with v2.4.29 on my local computer tcp_mem set to the following: cat /proc/sys/net/ipv4/tcp_mem 49152 65536 98304 (192MB) (256MB) (384MB) 2) When I boot the same computer with Knoppix v3.8.2 - v2.6.11.8 #3 cat /proc/sys/net/ipv4/tcp_mem 196608 262144 393216 (768MB) (1024MB) (1536MB) 3) When I boot the same computer with Slax v5.0.5 - v2.6.11.8 #1 cat /proc/sys/net/ipv4/tcp_mem 98304 131073 196608 (384MB) (512MB) (768MB) I can understand the change in the tcp stack from 2.4.x to 2.6.x. What I don't understand is why one level of the 2.6.11.8 #3 kernel will set my max TCP_MEM to 1.5 * MEMORY and the other 2.6.11.8 #1 sets TCP_MEM to .75 * MEMORY. Anyone one has any idea what is going on here??? I am trying to understand the tcp stack in Linux because I have to tune a GigE Linux based NFS/SMB server to as our departmental fileserver. The server is currently using the default tcp settings on 2.4.26 [patched to support quotas on RiserFS]. Thanks Paul - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
