From: David Miller <davem@davemloft.net>
To: billfink@mindspring.com
Cc: shemminger@linux-foundation.org, sangtae.ha@gmail.com,
rhee@eos.ncsu.edu, rhee@ncsu.edu, netdev@vger.kernel.org
Subject: Re: 2.6.20.7 TCP cubic (and bic) initial slow start way too slow?
Date: Wed, 13 Jun 2007 00:56:42 -0700 (PDT) [thread overview]
Message-ID: <20070613.005642.85685043.davem@davemloft.net> (raw)
In-Reply-To: <20070612233814.4b04db2f.billfink@mindspring.com>
From: Bill Fink <billfink@mindspring.com>
Date: Tue, 12 Jun 2007 23:38:14 -0400
> If there was a benefit, perhaps it would be useful to have a
> per-route option for setting the initial_ssthresh.
We have this per-route setting already, BIC and CUBIC just override it
with their local initial_ssthresh value when that is non-zero.
I wonder how many folks get tripped up by that totally unexpected
behavior. What's the point of the route metric we've had all of
these years if the congestion control algorithm is just going to
totally ignore it? That should never be the default behavior.
> OTOH just setting it to zero as a default should also be fine as
> that's the standard Reno behavior.
This is what I'm going to do.
Injong-ssi and Sangtae-ssi have had several weeks to give us final
guidance in this area, we cannot wait forever.
next prev parent reply other threads:[~2007-06-13 7:56 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 [this message]
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
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=20070613.005642.85685043.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=billfink@mindspring.com \
--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).