Thread (29 messages) flat view 29 messages, 7 authors, 2007-02-13

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

From: David Miller <davem@davemloft.net>
Date: 2007-02-12 22:53:52

From: Baruch Even <redacted>
Date: Tue, 13 Feb 2007 00:12:41 +0200
The problem is that you actually put a mostly untested algorithm as the
default for everyone to use. The BIC example is important, it was the
default algorithm for a long while and had implementation bugs that no
one cared for.
And if our TCP Reno implementation had some bugs, what should
we change the default to?  This is just idiotic logic.

These kinds of comments are just wanking, and lead to nowhere,
so please kill the noise.

If we have bugs in a particular algorithm, we should just fix
them.
As to the reasoning that the new algorithms are supposed to act like
Reno, that needs to be verified as well, it's not evident from the
code itself.
If you're not convinced and are intrested enough, then you should go
verify whether it is in fact true.  This is how things work.

If you find that it isn't true, great then we'll know about it and
have an opportunity to fix the bug.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help