On Fri, 7 Nov 2008, Daniel J Blueman wrote: > then we > avoid hurting these users by enabling ECN per default when eg > CONFIG_IP_ADVANCED_ROUTER is set (to little direct benefit of course). I suppose all distros enable that anyway in generic kernels so it's not going to be any different from just enabling it. > It's a start and a constructive idea; by doing this and documenting > it, we provide a wake-up call for vendors, laying the path for > enabling it for all types of host in a few years. Even enabling ECN > for -rc kernels will raise awareness. > > Alternatively, an ECN-day could be publicised targeting the linux tech > community, where we can report failing networks/sites to a central > website to quantify actual potential negative impact. This will still miss much. Eg., the ordering problems were not discovered afaik until 2.6.27 release, that's quite long time of testing without anybody noticing that hey it's broken (it might be that some distro circles saw this with some -rcx if they were using them but that didn't gain much attention until 2.6.27 was already out). And at that time the imminent release of Ubuntu's made the amount of testers much more abundant resource than with some other kernel version. Agreed that we definately should do more than just turn it on and wait for troubles but educating users might turn out to be quite hard problem. And certainly there will be troubles as even with the most comprehensive attempts within linux' dev+tester community are going to leave major holes like was proven with the tcp option ordering saga. -- i. -- To unsubscribe from this list: 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
