From: David Miller <davem@davemloft.net>
To: hannemann@nets.rwth-aachen.de
Cc: slot.daniel@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net/ipv4, linux-2.6.30.4
Date: Thu, 13 Aug 2009 13:13:28 -0700 (PDT) [thread overview]
Message-ID: <20090813.131328.70892070.davem@davemloft.net> (raw)
In-Reply-To: <4A8409CA.70200@nets.rwth-aachen.de>
From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Date: Thu, 13 Aug 2009 14:40:42 +0200
> David Miller schrieb:
>> From: Daniel Slot <slot.daniel@gmail.com>
>> Date: Wed, 12 Aug 2009 20:47:44 +0200
>>
>>> RFC 4653 specifies Non-Congestion Robustness (NCR) for TCP.
>>> In the absence of explicit congestion notification from the network, TCP
>>> uses loss as an indication of congestion.
>>> One of the ways TCP detects loss is using the arrival of three duplicate
>>> acknowledgments.
>>> However, this heuristic is not always correct,
>>> notably in the case when network paths reorder segments (for whatever
>>> reason), resulting in degraded performance.
>>
>> Linux's TCP stack already has sophisticated reordering detection.ä
>
>
> Hmm, sophisticated? Sorry, it seemed pretty rudimental/random to me.
It's more sophisticated than what you're proposing, which is a hammer
which requires intervention on the part of the application.
next prev parent reply other threads:[~2009-08-13 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bb6e06c00908121147h2dab7d0kf5841a40956c5c56@mail.gmail.com>
2009-08-12 21:55 ` [PATCH] net/ipv4, linux-2.6.30.4 David Miller
2009-08-13 12:40 ` Arnd Hannemann
2009-08-13 20:13 ` David Miller [this message]
2009-08-13 20:15 ` David Miller
2009-08-14 11:52 ` Daniel Slot
2009-08-12 18:59 Daniel Slot
-- strict thread matches above, loose matches on Subject: below --
2009-08-12 18:50 Daniel Slot
2009-08-12 19:02 ` Stephen Hemminger
2009-08-12 19:27 ` Daniel Slot
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=20090813.131328.70892070.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannemann@nets.rwth-aachen.de \
--cc=netdev@vger.kernel.org \
--cc=slot.daniel@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 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).