From: David Miller <davem@davemloft.net>
To: baruch@ev-en.org
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [patch 3/3] tcp: remove experimental variants from default list
Date: Mon, 12 Feb 2007 14:53:51 -0800 (PST) [thread overview]
Message-ID: <20070212.145351.35661569.davem@davemloft.net> (raw)
In-Reply-To: <20070212221241.GQ25760@galon.ev-en.org>
From: Baruch Even <baruch@ev-en.org>
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.
next prev parent reply other threads:[~2007-02-12 22:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 16:03 [patch 0/3] TCP trivial patches Stephen Hemminger
2007-02-12 16:03 ` [patch 1/3] tcp: cleanup of htcp Stephen Hemminger
2007-02-12 21:14 ` David Miller
2007-02-12 21:28 ` [patch 1/3] tcp: cleanup of htcp (resend) Stephen Hemminger
2007-02-12 21:34 ` David Miller
2007-02-12 16:03 ` [patch 2/3] tcp: use read mostly for CUBIC parameters Stephen Hemminger
2007-02-12 21:15 ` David Miller
2007-02-12 16:03 ` [patch 3/3] tcp: remove experimental variants from default list Stephen Hemminger
2007-02-12 19:11 ` Baruch Even
2007-02-12 20:13 ` Ian McDonald
2007-02-12 20:26 ` Stephen Hemminger
2007-02-12 20:34 ` David Miller
2007-02-12 20:32 ` David Miller
2007-02-12 20:37 ` Stephen Hemminger
2007-02-12 20:47 ` David Miller
2007-02-12 21:05 ` Ian McDonald
2007-02-12 20:20 ` David Miller
2007-02-12 22:12 ` Baruch Even
2007-02-12 22:53 ` David Miller [this message]
2007-02-13 9:56 ` Baruch Even
2007-02-13 16:49 ` SANGTAE HA
2007-02-13 17:42 ` Baruch Even
2007-02-13 19:54 ` John Heffner
2007-02-13 20:06 ` David Miller
2007-02-13 20:23 ` Stephen Hemminger
2007-02-13 17:41 ` Injong Rhee
2007-02-13 18:23 ` Baruch Even
2007-02-13 19:56 ` David Miller
2007-02-13 20:06 ` Baruch Even
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070212.145351.35661569.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=baruch@ev-en.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).