From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andreas Petlund <apetlund@simula.no>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Ilpo J?rvinen <ilpo.jarvinen@helsinki.fi>,
Eric Dumazet <eric.dumazet@gmail.com>,
Arnd Hannemann <hannemann@nets.rwth-aachen.de>,
LKML <linux-kernel@vger.kernel.org>,
shemminger@vyatta.com, David Miller <davem@davemloft.net>,
william.allen.simpson@gmail.com, damian@tvk.rwth-aachen.de,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [net-next PATCH v4 1/3] net: TCP thin-stream detection
Date: Sun, 21 Feb 2010 23:18:29 +0100 [thread overview]
Message-ID: <20100221221829.GX2659@nuttenaction> (raw)
In-Reply-To: <20100221102102.GB1311@ucw.cz>
* Pavel Machek | 2010-02-21 11:21:03 [+0100]:
>> +1) If the stream is thin, fast retransmit on the first dupACK.
>> +2) If the stream is thin, do not apply exponential backoff.
>
>2) seems very dangerous/unfair. If network congestion is caused just
>by thin streams, will the network just fall apart?
I question the fairness of this modification! The modification sounds _really_
far-reaching. Did you analyse the behaviour of this modification? What about
fairness analysis? Great work is available in the network simulator sector for
this kind of analysis (e.g. jain's fairness index).
HGN
--
Hagen Paul Pfeifer <hagen@jauu.net> || http://jauu.net/
Telephone: +49 174 5455209 || Key Id: 0x98350C22
Key Fingerprint: 490F 557B 6C48 6D7E 5706 2EA2 4A22 8D45 9835 0C22
next prev parent reply other threads:[~2010-02-21 22:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 14:40 [net-next PATCH v4 1/3] net: TCP thin-stream detection Andreas Petlund
2010-02-18 0:32 ` David Miller
2010-02-21 10:21 ` Pavel Machek
2010-02-21 11:23 ` Alexander Zimmermann
2010-02-21 20:04 ` Lars Eggert
2010-02-21 23:03 ` David Miller
2010-02-22 6:41 ` Lars Eggert
2010-02-22 6:41 ` Lars Eggert
2010-02-22 15:17 ` Andi Kleen
2010-02-22 15:17 ` Andi Kleen
2010-02-22 15:35 ` Alexander Zimmermann
2010-02-22 15:40 ` Andreas Petlund
2010-02-22 15:40 ` Andreas Petlund
2010-02-22 15:51 ` Andreas Petlund
2010-02-22 15:51 ` Andreas Petlund
2010-02-22 16:06 ` Hagen Paul Pfeifer
2010-02-22 16:06 ` Hagen Paul Pfeifer
2010-02-22 22:13 ` David Miller
2010-02-21 22:36 ` Ilpo Järvinen
2010-02-21 22:18 ` Hagen Paul Pfeifer [this message]
2010-02-21 22:31 ` Ilpo Järvinen
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=20100221221829.GX2659@nuttenaction \
--to=hagen@jauu.net \
--cc=apetlund@simula.no \
--cc=damian@tvk.rwth-aachen.de \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=hannemann@nets.rwth-aachen.de \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=shemminger@vyatta.com \
--cc=william.allen.simpson@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.