| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 14 Jul 2010 11:15:53 -0700 (PDT) From: David Miller <davem@...emloft.net> To: davidsen@....com Cc: lists@...dgooses.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: Raise initial congestion window size / speedup slow start? From: Bill Davidsen <davidsen@....com> Date: Wed, 14 Jul 2010 11:21:15 -0400 > You may have to go into /proc/sys/net/core and crank up the > rmem_* settings, depending on your distribution. You should never, ever, have to touch the various networking sysctl values to get good performance in any normal setup. If you do, it's a bug, report it so we can fix it. I cringe every time someone says to do this, so please do me a favor and don't spread this further. :-) For one thing, TCP dynamically adjusts the socket buffer sizes based upon the behavior of traffic on the connection. And the TCP memory limit sysctls (not the core socket ones) are sized based upon available memory. They are there to protect you from situations such as having so much memory dedicated to socket buffers that there is none left to do other things effectively. It's a protective limit, rather than a setting meant to increase or improve performance. So like the others, leave these alone too. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists