From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>,
aqm@ietf.org, Cake List <cake@lists.bufferbloat.net>
Subject: [Cerowrt-devel] upstreamed sqm sch_cake in openwrt-18.06-rc2
Date: Sun, 15 Jul 2018 20:34:33 -0700 [thread overview]
Message-ID: <CAA93jw507weB-rt2jPiqqgPgFOo==Ha9e6WsOgK16-yBf0D1Eg@mail.gmail.com> (raw)
hopefully the identical version of sch_cake that will also be in linux
4.19 (presently in net-next) is now in openwrt's 18.06-rc2 release. It
would be good for tons more folk to beat it up thoroughly over the
next several weeks before it is formally released.
Come on, don't you remember back when reflashing for the cause was fun?
https://downloads.openwrt.org/releases/18.06.0-rc2/targets/
For those of you not paying attention to sch_cake's development, see
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=046f6fd5daefac7f5abdafb436b30f63bc7c602b
1) It would be good to get back more results from docsis mode on cable
modems (where we hope now you can use 99.99% of the uplink set rate
rather than 85-95%). Also, If anyone's got docsis-3.1 with pie
enabled, it would be good to know if we co-exist well with that.
2) We hope everyone digs the default per-host/per flow fq
3) There's a zillion other features worth exercising, like diffserv. A
late addition was the ability to run at speeds far greater than the <=
1gbit speeds we initially targetted for the shaper component, on
suitable hw. (shaper works great at a gigabit, try it!) Establishing
good cpu constraints by architecture would be good too. Etc.
huge thx to kevin db, toke, jon, and everyone else for finally "making it real".
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next reply other threads:[~2018-07-16 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 3:34 Dave Taht [this message]
2018-07-16 17:09 Eric Johansson
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='CAA93jw507weB-rt2jPiqqgPgFOo==Ha9e6WsOgK16-yBf0D1Eg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@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