From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
Cc: "Baruch Even" <baruch@ev-en.org>,
"Dave Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [patch 3/3] tcp: remove experimental variants from default list
Date: Mon, 12 Feb 2007 12:26:34 -0800 [thread overview]
Message-ID: <20070212122634.07b3303b@freekitty> (raw)
In-Reply-To: <5640c7e00702121213p1430891el76e259aacd517c4a@mail.gmail.com>
On Tue, 13 Feb 2007 09:13:52 +1300
"Ian McDonald" <ian.mcdonald@jandi.co.nz> wrote:
> On 2/13/07, Baruch Even <baruch@ev-en.org> wrote:
> > * Stephen Hemminger <shemminger@linux-foundation.org> [070212 18:04]:
> > > The TCP Vegas implementation is buggy, and BIC is too agressive
> > > so they should not be in the default list. Westwood is okay, but
> > > not well tested.
> >
> > Since no one really agrees on the relative merits and problems of the
> > different algorithms and since the users themselves dont know, dont care
> > and have no clue on what should be the correct behaviour to report bugs
> > (see the old bic bugs, the htcp bugs, the recent sack bugs) I would
> > suggest to avoid making the whole internet a guinea pig and get back to
> > reno. If someone really needs to push high BDP flows he should test it
> > himself and choose what works for his kernel at the time.
> >
> > For myself and anyone who asks me I recommend to set the default to
> > reno. For the few who really need high speed flows, they should test
> > kernel and protocol combination.
> >
> > Baruch
>
> I agree wholeheartedly with Baruch. If we are going to remove BIC as
> default we should go back to Reno as Cubic is even less tested in
> production use than BIC.
>
> Unless of course the papers you saw at PFLDNET showed that Cubic was a
> really good choice and you want to point us to those papers.
No magic paper. But the impression from multiple talks is that Cubic
is still doing fine. Also for non high speed flows, it really doesn't matter
because all the loss based congestion controls behave the same.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-02-12 20:26 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 [this message]
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
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=20070212122634.07b3303b@freekitty \
--to=shemminger@linux-foundation.org \
--cc=baruch@ev-en.org \
--cc=davem@davemloft.net \
--cc=ian.mcdonald@jandi.co.nz \
--cc=netdev@vger.kernel.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).