From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Using PPPD pty option and script: controlling stdin buffer size?
Date: Wed, 13 Oct 2010 12:08:48 +0000 [thread overview]
Message-ID: <4CB5A150.2020908@workingcode.com> (raw)
In-Reply-To: <291B2C7721AC7B49AD11449A2883992E2E0DF561DB@SINTEFEXMBX01.sintef.no>
Arne Lie wrote:
> [Arne::] With all the respect, congestion control needs normally packet loss
> due to traffic overload to respond correctly, yes?
No. You've also got measurable delay, which I think is the key to
solving this problem.
> With the large buffering
> of stdin this do not happen before long... We're dealing with underwater
> networks with severely slow links and
> large propagation delays. We need relative short buffers to avoid seeing too
> big RTTs. Default PPP interfaces are set up with txqueuelen = 3, which is fine.
> However, when the *effective* queue size is this plus the stdin buffering, which
> we do not know the size of in bytes, but is in order of minutes (!) in RTT for such
> slow links, then it starts to get an annoyance.
What would you do if the "excessive" buffering were in some box in the
middle of the network? For many older systems, transmit queues of 50
packets or more are not at all uncommon.
I expect that an algorithm that tracks both round-trip latency and
throughput (using feedback from the peer) should be able to detect when
increasing the send rate only causes latency to go up and doesn't change
throughput. That's the optimal rate.
If you feel like hacking your kernel anyway then good luck with that,
but I suspect you'll be back to this problem in the future.
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
next prev parent reply other threads:[~2010-10-13 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 11:39 Using PPPD pty option and script: controlling stdin buffer size? Arne Lie
2010-10-12 14:31 ` walter harms
2010-10-12 14:36 ` Arne Lie
2010-10-12 15:18 ` James Carlson
2010-10-13 6:48 ` Arne Lie
2010-10-13 12:08 ` James Carlson [this message]
2010-10-13 12:19 ` Arne Lie
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=4CB5A150.2020908@workingcode.com \
--to=carlsonj@workingcode.com \
--cc=linux-ppp@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