All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Andreas Petlund <apetlund@simula.no>,
	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: Wed, 28 Oct 2009 16:31:32 +0200 (EET)	[thread overview]
Message-ID: <alpine.DEB.2.00.0910281618330.19761@wel-95.cs.helsinki.fi> (raw)
In-Reply-To: <4AE83FE4.1050309@nets.rwth-aachen.de>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1469 bytes --]

On Wed, 28 Oct 2009, Arnd Hannemann wrote:

> Eric Dumazet schrieb:
> > Andreas Petlund a écrit :
> >> This patch will make TCP use only linear timeouts if the stream is 
> >> thin. This will help to avoid the very high latencies that thin 
> >> stream suffer because of exponential backoff. This mechanism is only 
> >> active if enabled by iocontrol or syscontrol and the stream is 
> >> identified as thin. 

...I don't see how high latency is in any connection to stream being 
"thin" or not btw. If all ACKs are lost it usually requires silence for 
the full RTT, which affects a stream regardless of its size. ...If not all 
ACKs are lost, then the dupACK approach in the other patch should cover 
it already.

> However, addressing the proposal:
> I wonder how one can seriously suggest to just skip congestion response 
> during timeout-based loss recovery? I believe that in a heavily 
> congested scenarios, this would lead to a goodput disaster... Not to 
> mention that in a heavily congested scenario, suddenly every flow will 
> become "thin", so this will even amplify the problems. Or did I miss 
> something?

Good point. I suppose such an under-provisioned network can certainly be
there. I have heard that at least some people who remove exponential back 
off apply it later on nth retransmission as very often there really isn't 
such a super heavy congestion scenario but something completely unrelated 
to congestion which causes the RTO.

-- 
 i.

  reply	other threads:[~2009-10-28 14:31 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 [this message]
2009-10-29 13:51       ` Andreas Petlund
2009-10-29 14:24         ` Eric Dumazet
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
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=alpine.DEB.2.00.0910281618330.19761@wel-95.cs.helsinki.fi \
    --to=ilpo.jarvinen@helsinki.fi \
    --cc=apetlund@simula.no \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=hannemann@nets.rwth-aachen.de \
    --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 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.