On Tue, 9 Mar 2004 13:11:11 -0500 (EST) John Heffner <jheffner@psc.edu> wrote: > On Tue, 9 Mar 2004, Andi Kleen wrote: > > > > I would be very cautious about turning on Vegas by default. In certain > > > cases, it is exactly the right thing to do. However, in many cases it is > > > not. Vegas will end up losing when competing against regular Reno-ish > > > congestion control. Vegas also has issues with timer granularity, and > > > tuning its parameters can be quite tricky. There are a number of unusual > > > failure modes as well, such as responding to congestion on the reverse > > > path, or caused by cross traffic. > > > > It would be better to make it a per route flag than a global sysctl > > at least. > > This makes sense to me. One of the primary uses of Vegas I see in high > performance networking is as a work-around for grossly overbuffered > routers. This give the right level of control for that purpose. > > -John Every case I tested has vegas faster than the default reno. It is especially noticeable over the DSL. The current implementation is not ready to be turned on by default though. -- Stephen Hemminger mailto:shemminger@osdl.org Open Source Development Lab http://developer.osdl.org/shemminger - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
