From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: shemminger@vyatta.com, netdev@vger.kernel.org, ycheng@google.com
Subject: Re: [PATCH] tcp: Socket option to set congestion window
Date: Wed, 26 May 2010 00:33:07 -0700 (PDT) [thread overview]
Message-ID: <20100526.003307.112602435.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTinHGMtfw4Oydfgx0w7QLb-HyYSKdI-4smD-BEkq@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
Date: Wed, 26 May 2010 00:06:35 -0700
> It's really not that simple. In the application with multiple
> connections, congestion may only affect some number of connections, so
> more of the aggregate window may be preserved. This is an unfairness
> issue between 1 and N connection scenarios which is a real problem.
If this is true, then by all account your patch allows things to be
even worse.
Because now applications can still open up N connections, but with an
even larger initial CWND, with potentially exponential ramifications
on network congestion.
So yet another reason not to consider this feature seriously. It's
not an application level attribute, it's a network path one. Please
take it seriously because I really mean it.
next prev parent reply other threads:[~2010-05-26 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 5:01 [PATCH] tcp: Socket option to set congestion window Tom Herbert
2010-05-26 5:08 ` Stephen Hemminger
2010-05-26 5:52 ` David Miller
2010-05-26 7:06 ` Tom Herbert
2010-05-26 7:33 ` David Miller [this message]
2010-05-26 17:33 ` Andi Kleen
2010-05-26 17:41 ` Denys Fedorysychenko
2010-05-26 21:08 ` David Miller
2010-05-26 21:27 ` Andi Kleen
2010-05-26 22:10 ` David Miller
2010-05-26 22:29 ` Rick Jones
2010-05-27 7:57 ` Andi Kleen
2010-05-26 23:15 ` Hagen Paul Pfeifer
2010-05-27 3:04 ` David Miller
2010-05-27 7:08 ` Hagen Paul Pfeifer
2010-05-27 7:28 ` David Miller
2010-05-27 7:46 ` Hagen Paul Pfeifer
2010-05-27 16:14 ` Tom Herbert
2010-05-27 18:56 ` Andi Kleen
2010-05-27 19:19 ` Hagen Paul Pfeifer
2010-05-27 8:00 ` Andi Kleen
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=20100526.003307.112602435.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=therbert@google.com \
--cc=ycheng@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).