From: dpreed@reed.com
To: "Michael Richardson" <mcr@sandelman.ca>
Cc: cerowrt-users@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Cerowrt-users] QOS settings vs speedboost and random bandwidth
Date: Mon, 26 Nov 2012 10:04:11 -0500 (EST) [thread overview]
Message-ID: <1353942251.571510886@apps.rackspace.com> (raw)
In-Reply-To: <31933.1353939756@obiwan.sandelman.ca>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
You can use a small fraction of the capacity of the cable uplink path to measure its queueing delay dynamically, and when it gets longer than latency*"expected bitrate", reduce "expected bitrate".
You want to do this *as quickly as possible*, so what you do is insert a "link monitor" task in the driver that sends tiny probe packets addressed to the nearest "loopback point" you can find/create on the other side, and measure the RTT. You can use, for example, the technique used by traceroute, which is to set the hop count to the smallest number that causes a return ICMP packet to be sent, and send one of those periodically.
I used this specific technique to cause my uplink queue to move back into my router, where I could manage it. You can also use it for the downlink queue measurement, but it doesn't move the queue into the router smoothly, instead you have to drop/ECN-mark the IP frames coming in.
This can all be done between the IP layer and layer 2. Since it exploits speedboost better, it might be worth adding as an option to cerowrt, so you don't have to set a speed limit explicitly when you have a single connection to the public Internet.
-----Original Message-----
From: "Michael Richardson" <mcr@sandelman.ca>
Sent: Monday, November 26, 2012 9:22am
To: cerowrt-users@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Cerowrt-users] QOS settings vs speedboost and random bandwidth
>>>>> "Dave" == Dave Taht <dave.taht@gmail.com> writes:
Dave> to move the fq_codel algorithm into the cable modem, OR to have the
Dave> cable modem exert flow control like ADSL modems do. Then have the
Dave> smarter device (the router) then do smarter queuing.
I was unaware that DSL models were doing this... is this with GbE
ethernet level XON/XOFF? Should I assume that any DSL model with less
than a GbE sync doesn't/can't have it? Any brands you'd like to
acknowledge?
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 3059 bytes --]
next prev parent reply other threads:[~2012-11-26 15:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121125232034.GF24680@merlins.org>
2012-11-26 8:32 ` Dave Taht
2012-11-26 14:22 ` Michael Richardson
2012-11-26 15:04 ` dpreed [this message]
2012-11-26 15:38 ` Michael Richardson
2012-11-26 16:37 ` dpreed
2012-11-26 18:11 ` Michael Richardson
2012-11-26 19:23 ` Marc MERLIN
2012-11-26 19:58 ` dpreed
2012-11-26 21:27 ` Michael Richardson
2012-11-26 22:26 ` dpreed
2012-11-26 15:35 ` Jim Gettys
2012-11-26 18:13 ` Michael Richardson
2012-11-26 18:28 ` Jim Gettys
2012-11-26 21:29 ` Michael Richardson
2012-11-26 15:27 ` Jim Gettys
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1353942251.571510886@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cerowrt-users@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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