netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H.K. Jerry Chu" <hkjerry.chu@gmail.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, dccp@vger.kernel.org,
	therbert@google.com
Subject: Re: [PATCH] tcp: Increase the initial congestion window to 10.
Date: Thu, 3 Feb 2011 13:17:19 -0800	[thread overview]
Message-ID: <AANLkTimWHAz0SX_u42guHp2KNyQESsH6ysNwRoe7ZVJ=@mail.gmail.com> (raw)
In-Reply-To: <47859e9273bb0c1b2c32fc1adfa450ee@localhost>

On Thu, Feb 3, 2011 at 6:00 AM, Hagen Paul Pfeifer <hagen@jauu.net> wrote:
>
> On Wed, 02 Feb 2011 17:07:50 -0800 (PST), David Miller wrote:
>
>> +/* TCP initial congestion window */
>> +#define TCP_INIT_CWND                10
>> +
>
> Davem, there is _no_ research how this huge IW will behave in environments
> with a small BDP. Belief it or not, but there are networks out there with a
> BDP similar to ~1980. Why for heaven's sake should this work in these
> environments? There are only _two_ extensive analysis one from Cherry and
> and one from Ilpo. Both analysis focus on current mainstream BDP. I started

It's more than that. We have also conducted extensive, large scale
experiments covering
all BDP/RTT combinations and the result was documented in details in a
SIGCOMM/CCR paper that can be found from a summary page
http://code.google.com/speed/protocols/tcpm-IW10.html covering all our
IW10 work.

> to setup a ns-2 environment but due to lack of time I am a little bit
> behind schedule. Anyway, why not make this a tunable per route knob so that
> it is easier to fix things, e.g. set IW back to 3.

You've seemed to get this backwards. Shouldn't we set the default for the normal
cases and leave the corner cases to the initcwnd and initrwnd knobs to cover?

Jerry

>
> HGN
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  parent reply	other threads:[~2011-02-03 21:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03  1:07 [PATCH] tcp: Increase the initial congestion window to 10 David Miller
2011-02-03  1:53 ` Eric Dumazet
2011-02-03  3:34   ` David Miller
2011-02-03  2:25 ` Nandita Dukkipati
2011-02-03 14:00 ` Hagen Paul Pfeifer
2011-02-03 14:17   ` John Heffner
2011-02-03 14:26     ` Hagen Paul Pfeifer
2011-02-03 14:43   ` Hagen Paul Pfeifer
2011-02-03 21:17   ` H.K. Jerry Chu [this message]
2011-02-03 22:55     ` Hagen Paul Pfeifer
2011-02-03 20:28 ` Yuchung Cheng
     [not found] ` <AANLkTi=z-1-=R4X6hxs738jMEdYwfMPBFq9Ss-JwKCy3@mail.gmail.com>
2011-02-03 22:00   ` Leandro Melo de Sales
2011-02-05 13:58     ` Gerrit Renker
2011-02-03 22:43 ` Ilpo Järvinen
2011-02-03 23:54   ` Yuchung Cheng
2011-02-04 19:50     ` Ilpo Järvinen
2011-02-04  2:01   ` H.K. Jerry Chu
2011-02-04 19:43     ` Ilpo Järvinen
2011-02-05  3:39       ` Jerry Chu
2011-02-04  8:38 ` Alexander Zimmermann
2011-02-06  2:14   ` David Miller
2011-02-05 13:57 ` Gerrit Renker

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='AANLkTimWHAz0SX_u42guHp2KNyQESsH6ysNwRoe7ZVJ=@mail.gmail.com' \
    --to=hkjerry.chu@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dccp@vger.kernel.org \
    --cc=hagen@jauu.net \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.com \
    /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).