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: Tue, 12 Jun 2007 17:16:03 -0700 From: Stephen Hemminger <shemminger@...ux-foundation.org> To: David Miller <davem@...emloft.net> Cc: billfink@...dspring.com, 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? On Tue, 12 Jun 2007 15:12:58 -0700 (PDT) David Miller <davem@...emloft.net> wrote: > From: Bill Fink <billfink@...dspring.com> > Date: Wed, 16 May 2007 02:44:09 -0400 > > > [root@...g2 ~]# netstat -s | grep -i retrans > > 25446 segments retransmited > > 20936 fast retransmits > > 4503 retransmits in slow start > > 4 sack retransmits failed > > > > It then only took 2.14 seconds to transfer 1 GB of data. > > > > That's all for now. > > Thanks for all of your testing and numbers Bill. > > Inhong et al., we have to do something about this, the issue > has been known and sitting around for weeks if not months. > > How safely can we set the default initial_ssthresh to zero in > Cubic and BIC? Yes. set it to zero. The module parameter could even go, and just leave the route metric as a way to set/remember it. - 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