From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andreas Petlund <apetlund@simula.no>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
"Arnd Hannemann" <hannemann@nets.rwth-aachen.de>,
Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
shemminger@vyatta.com, "David Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/3] net: TCP thin linear timeouts
Date: Thu, 29 Oct 2009 15:24:07 +0100 [thread overview]
Message-ID: <4AE9A587.7050400@gmail.com> (raw)
In-Reply-To: <58396856-6D7E-4CE1-8D66-D1F11205B0D5@simula.no>
Andreas Petlund a écrit :
>
> The removal of exponential backoff on a general basis has been
> investigated and discussed already, for instance here:
> http://ccr.sigcomm.org/online/?q=node/416
> Such steps are, however considered drastic, and I agree that caution
> must be made to thoroughly investigate the effects of such changes.
> The changes introduced by the proposed patches, however, are not default
> behaviour, but an option for applications that suffer from the
> thin-stream TCP increased retransmission latencies. They will, as such,
> not affect all streams. In addition, the changes will only be active for
> streams which are perpetually thin or in the early phase of expanding
> their cwnd. Also, experiments performed on congested bottlenecks with
> tail-drop queues show very little (if any at all) effect on goodput for
> the modified scenario compared to a scenario with unmodified TCP streams.
>
> Graphs both for latency-results and fairness tests can be found here:
> http://folk.uio.no/apetlund/lktmp/
>
There should be a limit to linear timeouts, to say ... no more than 6 retransmits
(eventually tunable), then switch to exponential backoff. Maybe your patch
already implement such heuristic ?
True link collapses do happen, it would be good if not all streams wakeup in the same
second and make recovery very slow.
Thats too easy to accept possibly dangerous features with the excuse of saying
"It wont be used very much", because you cannot predict the future.
next prev parent reply other threads:[~2009-10-29 14:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 16:31 [PATCH 2/3] net: TCP thin linear timeouts Andreas Petlund
2009-10-27 16:56 ` Eric Dumazet
2009-10-28 12:58 ` Arnd Hannemann
2009-10-28 14:31 ` Ilpo Järvinen
2009-10-29 13:51 ` Andreas Petlund
2009-10-29 14:24 ` Eric Dumazet [this message]
2009-10-29 17:01 ` Rick Jones
[not found] ` <07CD1135-C68B-4264-8CD3-C4BC0400FDA2@simula.no>
2009-10-29 16:11 ` Arnd Hannemann
2009-10-28 3:20 ` William Allen Simpson
2009-10-29 13:50 ` Andreas Petlund
2009-10-28 14:18 ` Ilpo Järvinen
-- strict thread matches above, loose matches on Subject: below --
2009-10-29 15:14 apetlund
2009-10-29 15:19 apetlund
2009-10-29 15:43 apetlund
2009-10-29 15:50 ` Eric Dumazet
2009-10-29 20:52 ` Ilpo Järvinen
2009-10-29 16:54 apetlund
2009-10-30 10:48 apetlund
2009-10-30 17:33 ` Rick Jones
2009-10-30 18:11 ` William Allen Simpson
2009-11-05 13:37 ` Andreas Petlund
2009-10-30 15:27 apetlund
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=4AE9A587.7050400@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=apetlund@simula.no \
--cc=davem@davemloft.net \
--cc=hannemann@nets.rwth-aachen.de \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).