Re: [patch 3/3] tcp: remove experimental variants from default list

From: "SANGTAE HA" <redacted>
Date: Tue, 13 Feb 2007 11:49:47 -0500

I don't care what algorithm is default in kernel, however, it is not
appropriate to get back to Reno. As Windows decided to go with
"Compound TCP", why we want to back to 80's algorithm?

I want to re-emphasize this, in BIG BOLD LETTERS, that going back to
Reno is totally unacceptable recommendation to anyone in the current
internet environment.

In fact, it's a cop out to tell people they should use Reno instead
of one of the modern algorithms that can handle high BDP paths.

What is criteria for "untested"?  Who judges that this algorithm is
fully tested and is ready to use?

This is another excellent point.

Right now, in the end, the people who decide this are roughly
Stephen and myself.  So we do need to read the papers (we did),
think about the algorithm, and figure out what's best for Linux.
And that means balancing each possibility with each reasonable
alternative, and Reno is NOT a reasonable alternative.

And right now what's best for Linux, from our perspective, is a
default of CUBIC.

Then, what do you want to make a default? You want to get back to
BIC? or Reno?

Baruch has already stated that he recommends people to use Reno.