From: David Miller <davem@davemloft.net>
To: dccp@vger.kernel.org
Subject: Re: Sensitivity of TFRC throughput equation wrt to changes of RTT
Date: Fri, 13 Apr 2007 20:43:56 +0000 [thread overview]
Message-ID: <20070413.134356.18297036.davem@davemloft.net> (raw)
In-Reply-To: <200704131303.03072@strip-the-willow>
From: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
Date: Sat, 14 Apr 2007 07:52:32 +1200
> Which comes into play when we have loss. When we have no loss, or a
> long period of non-loss we can send as fast as we want according to
> the spec. This should normally be the case on LANs where the RTT makes
> a far bigger difference.
This is correct, also there is another related issue I should
have mentioned.
Congestion control on LANs and very small RTTs arguably does not make
much sense. Many very smart networking folk have argued this.
The reason is that any congestion you detect on a LAN will go away
long before you can even react to it in a protocol stack.
Alexey Kuznetsov once was trying to come up with a statistical
theoretical model to justify this in some tangible way, but he
never came up with anything concrete.
It's funny but the RTT measurements of TCP have a minimum which
is established by the timer granularity limitations of the original
TCP implementation in BSD. See the TCP_RTO_MIN clamping we do
in the Linux TCP stack.
Although originally an implementation side-effect, it plays into
the LAN issues I discussed above.
next prev parent reply other threads:[~2007-04-13 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 12:03 Sensitivity of TFRC throughput equation wrt to changes of RTT Gerrit Renker
2007-04-13 19:33 ` David Miller
2007-04-13 19:52 ` Ian McDonald
2007-04-13 20:27 ` Gerrit Renker
2007-04-13 20:43 ` David Miller [this message]
2007-04-13 20:54 ` David Miller
2007-04-14 5:43 ` Eddie Kohler
2007-04-15 16:15 ` Gerrit Renker
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=20070413.134356.18297036.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
/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