netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: ian.mcdonald@jandi.co.nz, baruch@ev-en.org, netdev@vger.kernel.org
Subject: Re: [patch 3/3] tcp: remove experimental variants from default list
Date: Mon, 12 Feb 2007 12:37:13 -0800	[thread overview]
Message-ID: <20070212123713.1e8efb0d@freekitty> (raw)
In-Reply-To: <20070212.123240.21597176.davem@davemloft.net>

On Mon, 12 Feb 2007 12:32:40 -0800 (PST)
David Miller <davem@davemloft.net> wrote:

> From: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
> Date: Tue, 13 Feb 2007 09:13:52 +1300
> 
> > 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.
> 
> I heavily dislike all of these "reactionary" patches from Stephen
> after he attended PFDLNET.
> 
> If he never went there, none of these patches would have been
> proposed.  He went to the sermon and he became converted :-)

My patches weren't reactionary. Going to pure old Reno is reactionary.
It was more looking at the state of the code on the flight back
and cleaning house. Others were/are reactionary. 


> We want people to play with this stuff, and they can experiment
> regardless of whatever options or even code we put into the kernel.
> Every user can muck with the congestion control on their computer
> however they want, and THAT'S GOOD!
> 
> Sure we indirectly recommend to distribution vendors what to use
> by default by the Kconfig defaults we put into the vanilla tree,
> and that's fine too.
> 
> Even after reading all of the papers, I still think CUBIC or even BIC
> by default is not all that controbersal or radical thing to use by
> default.
> 
> I'm sorry if the researchers and IETF folks don't like this.  Too bad,
> get over it.

I push the problem back in their court: "Why do you not have a process
that causes consensus?" IETF has done nothing to create any incentive
for long term cooperation.

> If you use RENO you're stupid, since performance is going to stink for
> absolutely normal connections.  Fact: high BDP pipes are everywhere,
> even grandma has one.  So just taking out the best solution we have
> for that problem currently because it's not perfect is not the answer.
> 

Do I need to dig out the "Why Reno sucks" graphs?

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

  reply	other threads:[~2007-02-12 20:37 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 [this message]
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=20070212123713.1e8efb0d@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).