<p dir="ltr">How good is the throughput on CeroWrt compared to OpenWrt ?</p>
<div class="gmail_quote">On Oct 2, 2014 9:55 AM, "Dave Taht" <<a href="mailto:dave.taht@bufferbloat.net">dave.taht@bufferbloat.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Oct 01, 2014 at 12:10:46PM -0400, Weedy wrote:<br>
> On 30/03/14 06:29 PM, Dave Taht wrote:<br>
> > On Sun, Mar 30, 2014 at 02:24:44PM -0400, Weedy wrote:<br>
> >> On Sat, Mar 29, 2014 at 2:56 PM, Dave Täht <<a href="mailto:dave.taht@bufferbloat.net">dave.taht@bufferbloat.net</a>>wrote:<br>
> >><br>
> >>> From: Dave Taht <<a href="mailto:dave.taht@bufferbloat.net">dave.taht@bufferbloat.net</a>><br>
> >>><br>
> >>> This adds support for the bufferbloat project's "Smart Queue Management"<br>
> >>> (SQM) system, which improves over openwrt's qos-scripts in the following<br>
> >>> ways<br>
> >>><br>
> >>> + Uses HTB with two models for managing traffic<br>
> >>> a simplest one that merely uses fq_codel, and a three tier one that does<br>
> >>> some basic and tunable packet prioritization.<br>
> >>><br>
> >>> + Works with ipv6 and ipv4 correctly (unlike qos-scripts)<br>
> >>> + extensive support for fixing ADSL and PPOe framing problems<br>
> >>> + Partial support for key diffserv markings<br>
> >>> + highly tuned fq_codel implementation especially for low bandwidths<br>
> >>> + Tested heavily on cable modems and on dsl devices<br>
> >>><br>
> >>> It is a disimprovement in that:<br>
> >>><br>
> >>> - There are no built-in tricks for doing l7 classification,<br>
> >>> or other forms of packet inspection.<br>
> >>><br>
> >>> - We haven't explored hfsc all that much, prefering to rely<br>
> >>> on the predictable behavior of htb + fq_codel for everything<br>
> >>><br>
> >>> - And there is support for a few qdiscs that are not in the linux<br>
> >>> kernel mainline that remain experimental.<br>
> >>> ---<br>
> >>> net/sqm-scripts/Makefile | 48 +++<br>
> >>> net/sqm-scripts/files/etc/config/sqm | 11 +<br>
> >>> net/sqm-scripts/files/etc/init.d/sqm | 23 ++<br>
> >>> net/sqm-scripts/files/usr/lib/sqm/functions.sh | 335<br>
> >>> ++++++++++++++++++++<br>
> >>> net/sqm-scripts/files/usr/lib/sqm/run.sh | 67 ++++<br>
> >>> net/sqm-scripts/files/usr/lib/sqm/simple.qos | 187 +++++++++++<br>
> >>> net/sqm-scripts/files/usr/lib/sqm/simple.qos.help | 1 +<br>
> >>> net/sqm-scripts/files/usr/lib/sqm/simplest.qos | 84 +++++<br>
> >>> .../files/usr/lib/sqm/simplest.qos.help | 1 +<br>
> >>> net/sqm-scripts/files/usr/lib/sqm/stop.sh | 22 ++<br>
> >>> 10 files changed, 779 insertions(+)<br>
> >>> create mode 100644 net/sqm-scripts/Makefile<br>
> >>> create mode 100644 net/sqm-scripts/files/etc/config/sqm<br>
> >>> create mode 100755 net/sqm-scripts/files/etc/init.d/sqm<br>
> >>> create mode 100644 net/sqm-scripts/files/usr/lib/sqm/functions.sh<br>
> >>> create mode 100755 net/sqm-scripts/files/usr/lib/sqm/run.sh<br>
> >>> create mode 100755 net/sqm-scripts/files/usr/lib/sqm/simple.qos<br>
> >>> create mode 100644 net/sqm-scripts/files/usr/lib/sqm/simple.qos.help<br>
> >>> create mode 100755 net/sqm-scripts/files/usr/lib/sqm/simplest.qos<br>
> >>> create mode 100644 net/sqm-scripts/files/usr/lib/sqm/simplest.qos.help<br>
> >>> create mode 100755 net/sqm-scripts/files/usr/lib/sqm/stop.sh<br>
> >>><br>
> >>> diff --git a/net/sqm-scripts/files/etc/config/sqm<br>
> >>> b/net/sqm-scripts/files/etc/config/sqm<br>
> >>> new file mode 100644<br>
> >>> index 0000000..547d321<br>
> >>> --- /dev/null<br>
> >>> +++ b/net/sqm-scripts/files/etc/config/sqm<br>
> >>> @@ -0,0 +1,11 @@<br>
> >>> +<br>
> >>> +config queue 'ge00'<br>
> >>> + option enabled '0'<br>
> >>> + option interface 'ge00'<br>
> >>> + option download '20000'<br>
> >>> + option upload '4000'<br>
> >>> + option qdisc 'fq_codel'<br>
> >>> + option script 'simple.qos'<br>
> >>> + option qdisc_advanced '0'<br>
> >>> + option linklayer 'none'<br>
> >>> +<br>
> >>><br>
> >><br>
> >> How hard is this to config from the command line/vim?<br>
> ><br>
> > There are a few more options than this (for DSL compensation, ecn<br>
> > and advanced configuration), the above would work if you changed<br>
> > enabled to '1' and the device from ge00 to your wan device. (not<br>
> > the "wan" firewall rule, presently. )<br>
> ><br>
> > It does help to have a sane long term and realistic measurement of your<br>
> > network using something like the rrul test rather than the oft-gamed speedtest.<br>
> ><br>
> > <a href="http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_SQM_for_CeroWrt_310" target="_blank">http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_SQM_for_CeroWrt_310</a><br>
> ><br>
> > You are right, we should fully document all the variables in this file.<br>
> > Until recently they were kind of in flux.<br>
> ><br>
> >> I've never needed or really wanted luci on my box, I just use vim. Going by<br>
> >> this patch, there is either nothing to config or no examples. I would think<br>
> >> shipping a roughly equivalent config to what ships in qos-scripts would be<br>
> >> a good start to get people testing.<br>
> ><br>
> > /etc/init.d/sqm start,stop etc work as expected.<br>
> ><br>
> >> IE: highest priority: small ARP, DNS, and SSH packets<br>
> ><br>
> > The SQM default is local DNS and ntp. fq_codel automagically optimizes<br>
> > for other sparse flows like arp, ssh, mosh, tcp syn, synack, etc,<br>
> > no need to do that via classification.<br>
> ><br>
> >> normal: HTTP, HTTPS<br>
> ><br>
> > So you want to deprioritize vpn, smtp, rsync, dropbox, http on odd ports,<br>
> > caching servers, etc, all in favor of the web gods?<br>
> ><br>
> > we just toss all that into the normal (best effort bin) and let fq_codel<br>
> > sort it out.<br>
> ><br>
> >> bulk: everything else.<br>
> ><br>
> > We do respect the diffserv marking of CS1 (background) and toss it<br>
> > into the background queue.<br>
> ><br>
> >> Side note: Will SQM do bandwidth slicing? Or at least handle "hostile"<br>
> >> environments better? I say "hostile" as in roommates or maybe teenage kids.<br>
> >> Multiple people/devices thinking they are entitled to the entire WAN<br>
> >> bandwidth at all times.<br>
> ><br>
> > fq_codel does fair (well, we call it "flow") queuing.<br>
> ><br>
> > <a href="https://tools.ietf.org/html/draft-hoeiland-joergensen-aqm-fq-codel-00" target="_blank">https://tools.ietf.org/html/draft-hoeiland-joergensen-aqm-fq-codel-00</a><br>
> ><br>
> > And manages the depth of flows via codel.<br>
> ><br>
> > <a href="http://tools.ietf.org/html/draft-nichols-tsvwg-codel-02" target="_blank">http://tools.ietf.org/html/draft-nichols-tsvwg-codel-02</a><br>
> ><br>
> > In other words, it will be fair to all fat flows generated by everyone,<br>
> > and slice flows down to the defined quantum and turn them back into<br>
> > packets.<br>
> ><br>
> > The "simplest.qos" model in SQM works remarkably well without trying to<br>
> > classify anything at all. I encourage people to try merely that and have<br>
> > their preconceptions altered.<br>
> ><br>
> > The three-tier model (simple.qos), is more like what people think they want,<br>
> > but the default is set to the bare minimum of what worked well in testing.<br>
> ><br>
> > Example: a lot of flows are marked CS1 that shouldn't be, and starving<br>
> > that queue to like 5% rather than it's current 30% turned out badly.<br>
> ><br>
> > In terms of identifying and "punishing" abusers, well, the only thing<br>
> > that stresses this code out even the slightest is dozens of torrent flows.<br>
> ><br>
> > Give it a shot. :)<br>
> ><br>
> I feel like this died.<br>
<br>
It didn't die.<br>
<br>
*I* died.<br>
<br>
I'd been on a death march for the last 8 months trying to<br>
get the last bugs out of openwrt/cerowrt, and when the last big one<br>
got fixed (bug 442 in the cerowrt database, multiple other trackers)<br>
<br>
I put out a release of 3.10.50-1 pre BBrc1 and went to sleep.<br>
<br>
When I woke up, about a week ago, everybody had nearly 2 months<br>
uptime, good throughput, and a bunch of minor nits here and there.<br>
<br>
Hooray!<br>
<br>
The prospect of resyncing with BBrcX intimidates me, and I have<br>
had a ton of other things that slid to take care of, so I've<br>
been catching up on those. Sebastian has been taking<br>
care of SQM nits...<br>
<br>
<a href="https://github.com/dtaht/ceropackages-3.10/issues/8" target="_blank">https://github.com/dtaht/ceropackages-3.10/issues/8</a><br>
<br>
And Jonathon morton has been pouring it all into<br>
pure C - with an integral bandwidth shaper that we<br>
hope will be faster and more efficient than htb.<br>
<br>
See an early result:<br>
<br>
<a href="http://pastebin.com/zz06WhJr" target="_blank">http://pastebin.com/zz06WhJr</a><br>
<br>
It takes much of the heavy lifting out of the existing<br>
sqm scripts.<br>
<br>
tc qdisc add dev eth1 root cake bandwidth 80mbit<br>
<br>
<br>
So I don't know where to go. Certainly I'd like to<br>
see the battle hardened sqm scripts (which are more<br>
flexible than the C code above) get more widely used<br>
and in BB.<br>
<br>
openwrt users can do that today by adding the ceropackages repo to their build system.<br>
or just installing the sqm-scripts and luci-app-sqm.<br>
<br>
or we can clean it up further for openwrt mainline.<br>
<br>
But I haven't seen one core openwrt dev say, yes, we want this mainlined, here's what you need to fix, so I'm inclined to go back to my cave, get more sleep, and work on the successor.<br>
_______________________________________________<br>
openwrt-devel mailing list<br>
<a href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a><br>
<a href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel" target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
</blockquote></div>