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, 13 Jun 2007 00:56:42 -0700 (PDT) From: David Miller <davem@...emloft.net> To: billfink@...dspring.com Cc: shemminger@...ux-foundation.org, sangtae.ha@...il.com, rhee@....ncsu.edu, rhee@...u.edu, netdev@...r.kernel.org Subject: Re: 2.6.20.7 TCP cubic (and bic) initial slow start way too slow? From: Bill Fink <billfink@...dspring.com> Date: Tue, 12 Jun 2007 23:38:14 -0400 > If there was a benefit, perhaps it would be useful to have a > per-route option for setting the initial_ssthresh. We have this per-route setting already, BIC and CUBIC just override it with their local initial_ssthresh value when that is non-zero. I wonder how many folks get tripped up by that totally unexpected behavior. What's the point of the route metric we've had all of these years if the congestion control algorithm is just going to totally ignore it? That should never be the default behavior. > OTOH just setting it to zero as a default should also be fine as > that's the standard Reno behavior. This is what I'm going to do. Injong-ssi and Sangtae-ssi have had several weeks to give us final guidance in this area, we cannot wait forever. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists