Yes, it can easily changed at runtime, but this is not the usage bug we have.
All the users of Ubuntu Intrepid will get penalised by the poor scaling and unfairness of TCP Reno (using blind congestion control [1]), which is why TCP cubic was introduced and became default in 2.6.19, some 2 years ago; all the high-profile distros are sure to enable this per default, since TCP Reno suffers in particular use patterns, such as wireless (ie lossy net) throughput, fairness on congested networks (eg xDSL), throughput on high BDP networks (eg internet), plus it'll get worse as the bandwidth product of xDSL lines increased, but latency doesn't decrease (due to c). I want people using Intrepid to be able to achieve the best experience on Ubuntu, not have to move to SuSE or Redhat, or publish benchmarks showing penalties on Ubuntu (eg from Phoronix), but perhaps we have to wait another 6 months again? --- [1] http://www.powerset.com/explore/semhtml/Taxonomy_of_congestion_control?query=CUBIC+TCP -- 2.6.27 default TCP congestion control regression... https://bugs.launchpad.net/bugs/278801 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
