From: dave taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Cerowrt-devel] preliminary codel and fq_codel support for cerowrt
Date: Wed, 16 May 2012 10:09:01 -0700 [thread overview]
Message-ID: <4FB3DF2D.3070109@gmail.com> (raw)
In-Reply-To: <6F884B65-4388-4655-8B03-4B7936ABCDE0@gmx.de>
On 05/16/2012 09:34 AM, Sebastian Moeller wrote:
> Hi Dave,
>
> so I upgraded my router to the most recent version, and hey I am really impressed, thanks a lot for all the work.
> (I never really stress the local network, and the internet is 5/30 so I consider to be on the safe side of #379 and decided to ignore your recommendation about the suitability for main routers).
> I tried the simple_qos.sh script and for my testing it is quite nice indeed. The whole network stays quite responsive even during abuse. The whole expeience was quite pleasant (using ssh over a ssl based VPN to remote control an X11 session while stressing in and out direction); counter to my subjective experience though netalyzr was detecting 3000 odd milliseconds of buffering upstream (downstream was fine). Once I find more time I will have a go at reproducing that. (Now I have to figure out whether I need to restart simple_qos.sh anytime I down or up an interface; any pointer?) BTW, how do you envision this to be started under the AQM tab; shall this start simple_qos or rather debloat?
No, I had something more wonderful in mind.
Felix Fietkau has added fq_codel to the openwrt 3.3 kernel and to the
existing qos-scripts as of openwrt revision 31761.
Builds for 37 architectures and ~150 platforms are popping out as I write.
See
http://buildbot.openwrt.org:8010/one_line_per_build
For details.
I will be obsoleting the CeroWrt aqm and aqm-scripts and simple_qos as
soon as the new qos-scripts handles ipv6 properly, and maybe get a
chance to add a trick or two to more to it.
Erics latest patch to fq_codel has not yet landed in openwrt.
> Small observation, port 81 on the router seems open to the internet, easily fixed, but maybe something you might want know :)
Patches gladly accepted. Frankly I'd hoped to have CeroWall done by now,
but, well, the ball's on the 20 yard line, and I need to bench myself
for a while.
Hopefully someone else can take it in for the score.
>
> Anyway, thanks again
> Sebastian
>
>
> On May 14, 2012, at 1:59 PM, Dave Taht wrote:
>
>> A test release of CeroWrt is now available that has support for Kathie
>> Nichols' and Van Jacobson's new AQM, Codel , and Eric Dumazet's new
>> fair queuing implementation on top of that, fq_codel.
>>
>> fq_codel is enabled on all interfaces by default. It is vastly simpler
>> than what we were using before (sfqred) and draws upon and improves on
>> the same body of ideas (head drop, fq, timestamping) but is now tied
>> to Kathie and Van's blinding insights as to a good drop strategy, and
>> Eric's successor-to-sfqred ideas as towards head of queue behavior,
>> modern amounts of flows, and cache line optimizations.
>>
>> There is a simple_qos.sh script that can be set to your uplink and
>> downlink speeds, but no uci interface for it as yet, nor gui. (help on
>> finishing aqm-scripts and the luci interface gladly accepted)
>>
>> To see all the chocolately goodness of what fq_codel can do to wired
>> and wireless latency, it would be good for more to play with it.
>>
>> Benchmarks have been very good thus far, and more benchmarks and
>> analysis are highly desired.
>>
>> Caveat:
>>
>> This release suffers from an unrelated bug ( #379 ) and should NOT be
>> installed as your main router. I would love to beat this bug because
>> it's the only prio 1 remaining but thus far, no luck. Under lighter
>> loads CeroWrt appears to work just fine, but that's for me. YMMV.
>>
>> Get it here: http://huchra.bufferbloat.net/~cero1/3.3/3.3.6-2/
>>
>>
>> --
>> Dave Täht
>> SKYPE: davetaht
>> US Tel: 1-239-829-5608
>> http://www.bufferbloat.net
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2012-05-16 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 20:59 [Codel] " Dave Taht
2012-05-14 21:58 ` [Codel] [Cerowrt-devel] " Outback Dingo
2012-05-16 16:34 ` Sebastian Moeller
2012-05-16 17:09 ` dave taht [this message]
2012-05-16 17:16 ` Outback Dingo
2012-05-16 17:52 ` Dave Taht
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB3DF2D.3070109@gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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