From: Bill Fink <billfink@mindspring.com>
To: David Miller <davem@davemloft.net>
Cc: shemminger@linux-foundation.org, sangtae.ha@gmail.com,
rhee@eos.ncsu.edu, rhee@ncsu.edu, netdev@vger.kernel.org
Subject: Re: [PATCH] TCP: remove initial_ssthresh from Cubic
Date: Thu, 14 Jun 2007 00:03:41 -0400 [thread overview]
Message-ID: <20070614000341.b9151782.billfink@mindspring.com> (raw)
In-Reply-To: <20070613.114621.85409138.davem@davemloft.net>
On Wed, 13 Jun 2007, David Miller wrote:
> From: Stephen Hemminger <shemminger@linux-foundation.org>
> Date: Wed, 13 Jun 2007 11:31:49 -0700
>
> > Maybe it is time to remove BIC?
>
> I don't see any compelling reason, the same could be said
> of the other experimental protocols we include in the tree.
I agree bic should be kept. As I pointed out, if someone did want
to set the bic/cubic initial_ssthresh to 100 globally, my tests
showed bic's performance during the initial slow start phase was
far superior to cubic's. I don't know if this is a bug or a
feature with cubic.
-Bill
prev parent reply other threads:[~2007-06-14 4:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 0:37 2.6.20.7 TCP cubic (and bic) initial slow start way too slow? Bill Fink
2007-05-08 9:41 ` SANGTAE HA
2007-05-09 6:31 ` Bill Fink
2007-05-10 15:32 ` Bill Fink
2007-05-10 17:31 ` SANGTAE HA
2007-05-10 18:39 ` rhee
2007-05-10 20:35 ` David Miller
2007-05-10 20:45 ` Stephen Hemminger
2007-05-10 20:57 ` Injong Rhee
2007-05-12 16:07 ` Bill Fink
2007-05-12 16:45 ` SANGTAE HA
2007-05-16 6:44 ` Bill Fink
2007-06-12 22:12 ` David Miller
2007-06-13 0:16 ` Stephen Hemminger
2007-06-13 3:38 ` Bill Fink
2007-06-13 7:56 ` David Miller
2007-06-13 17:27 ` [PATCH] TCP: remove initial_ssthresh from Cubic Stephen Hemminger
2007-06-13 18:26 ` David Miller
2007-06-13 18:31 ` Stephen Hemminger
2007-06-13 18:46 ` David Miller
2007-06-14 4:03 ` Bill Fink [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=20070614000341.b9151782.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rhee@eos.ncsu.edu \
--cc=rhee@ncsu.edu \
--cc=sangtae.ha@gmail.com \
--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).