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 12:20:58 -0800 (PST) [thread overview]
Message-ID: <20070212.122058.63127043.davem@davemloft.net> (raw)
In-Reply-To: <20070212191101.GP25760@galon.ev-en.org>
From: Baruch Even <baruch@ev-en.org>
Date: Mon, 12 Feb 2007 21:11:01 +0200
> 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.
We have "high BDP flows" even going from between the east and the west
coast of the United States.
This doesn't even begin to touch upon extremely well connected
coutries like South Korea and what happens when people there try to
access sites in Europe or the US.
Good high BDP flow handling is necessary now and for everyday usage of
the internet, it's not some obscure thing only researchers in fancy
labs need.
This also isn't the internet of 15 years ago where IETF members can
spend 4 or 5 years masterbating over new ideas before deploying them.
I know that's what conservative folks want, but it isn't going to
happen.
next prev parent reply other threads:[~2007-02-12 20:20 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 [this message]
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=20070212.122058.63127043.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).