From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] edgerouter fq_codel notes
Date: Thu, 17 Jul 2014 10:32:08 -0700 [thread overview]
Message-ID: <CAA93jw7j5LmOKhCwqWnx=x=dRDbz2zvQ8ud_4+3NHOs2G6OOZA@mail.gmail.com> (raw)
A few months back I took a timeout (pair of weekends!) to get fq_codel
up and running on the edgerouter series of products from ubiquiti. It
was nice to have a chance to deal with questions from a new audience,
see what went wrong at higher rates, reframe my arguments, explain
stuff in general, and deal with a whole new set of bugs....
registration and joining the developer program is required to see the
enormous (230+ messages!) thread generated, which grew increasingly
philosophical towards the end...
http://community.ubnt.com/t5/EdgeMAX-Beta/Testing-fq-codel-in-v1-5-0beta1/td-p/828626
In the long run I hope to use this enormous volume of text and links
in some new writing(s), particularly on BQL, but if you are bored of
the slow traffic here, have fun over there. There were also about 10
subthreads generated throughout the site, if you search for fq_codel.
Although I like the edgerouter series a lot (the pro has been really
helpful in my lab), it does seem like a significant amount of work is
needed to make it do what I wanted (good >200mbit inbound qos), well,
and while that work continues (there is much buried potential in the
hardware!), I keep looking for easier wins. Certainly even the
edgerouter lite outperforms cerowrt across the board.
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
reply other threads:[~2014-07-17 17:32 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='CAA93jw7j5LmOKhCwqWnx=x=dRDbz2zvQ8ud_4+3NHOs2G6OOZA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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