From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Cc: jb <justinbeech@gmail.com>
Subject: [Cerowrt-devel] Nice Readme/Video on ipfire.org
Date: Mon, 20 Apr 2015 12:45:49 -0400 [thread overview]
Message-ID: <8C6D50D4-A9F9-4D98-AB4E-91BA7B6D121A@gmail.com> (raw)
Google Alerts showed me a link to the following presentation about bufferbloat, and using fq_codel to vanquish it.
http://wiki.ipfire.org/en/configuration/services/qos
https://www.youtube.com/watch?v=XB3w09VZn7g
N0mantech does a very good job. He shows how to configure the up and down bit rates for his IPfire router, the effect without and after turning it on. (He sort of skips over how the SQM allows it to control download buffering, but shows that it works.)
His conclusion: "The solution to having low latency is to have a router that has AQM in it." Pretty on-target.
reply other threads:[~2015-04-20 16:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8C6D50D4-A9F9-4D98-AB4E-91BA7B6D121A@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=justinbeech@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