From: "David S. Miller" <davem@redhat.com>
To: "Angelo Dell'Aera" <buffer@antifork.org>
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: TCP congestion control article
Date: Tue, 29 Jun 2004 12:44:18 -0700 [thread overview]
Message-ID: <20040629124418.54bfe820.davem@redhat.com> (raw)
In-Reply-To: <20040629203418.0a844a5b.buffer@antifork.org>
On Tue, 29 Jun 2004 20:34:18 +0200
"Angelo Dell'Aera" <buffer@antifork.org> wrote:
> First of all I know not too much about BITCP but I think it's unsafe
> to enable it by default... just like it's unsafe to enable by default
> any kind of new congestion control algorithm.
I disagree. In Stephen Hemminger and my own usage, BICTCP even
improved performance in cases where we had mistakenly misconfigured
our systems. That, frankly, is impressive.
Because it deals with long-fat-pipe issues as well, was another reason
we choose to enable it over westwood+.
> Another thing. I think it's necessary to provide some mechanism for
> enabling just one of these algorithms at a time.
We do, you turn one on and another one off. :-)
I discussed this with Stephen the other week. We came to the conclusion
that enabling both algorithms at the same time is valid, and we should
not put obstacles in the way to prevent people who wish to do this.
It might even be beneficial in some situations.
I agree with your analysis of Vegas, and that is why I did not enable it
by default. It has it's own set of problems, although I like many
aspects of it.
prev parent reply other threads:[~2004-06-29 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 10:39 TCP congestion control article Angelo Dell'Aera
2004-06-25 16:11 ` David S. Miller
2004-06-29 18:34 ` Angelo Dell'Aera
2004-06-29 19:44 ` David S. Miller [this message]
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=20040629124418.54bfe820.davem@redhat.com \
--to=davem@redhat.com \
--cc=buffer@antifork.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).