From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 3.10.10-1 development build released
Date: Wed, 11 Sep 2013 10:36:12 +0200 [thread overview]
Message-ID: <E07E6678-32FB-4A9A-A496-14CC4B83564F@gmx.de> (raw)
In-Reply-To: <CAA93jw4M=NqHRo8J7ned79vU9wyLLttn-OG9ifpSrAGmzBi3OA@mail.gmail.com>
Hi Dave,
so I ant for the shiny 3.10.11-2, worked great (using Fred's mtd -r method, thanks Fred)
On Sep 10, 2013, at 02:28 , Dave Taht <dave.taht@gmail.com> wrote:
> + readlink fix (hopefully fixes sysupgrade)
I guess this will be testable at the next version update...
> + usual merge with openwrt head (tons of ath9k changes)
Oh, as if you knew that I had a number of:
ath: phy1: Failed to stop TX DMA, queues=
lines in dmesg, quick testing did not allow me to get those with 3.10.11-2, but I will need to test further...
> + dnsmasq 2.67test10
> + ipv6subtrees back in
> + the final htb atm patches
So I tested tc_stab and htb_private from the AQM tab, both work equally well.
> + eliminated maxpacket check in codel
>
> - did not fold in edumazet's new fq code
> - 100% totally untested. May a braver soul than I give it a shot. I won't be near a cero box til thursday, otherwise.
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.10-1/
>
> -I'm not sure if I got the "last" of the aqm gui patches in there or not…
I think so, at least it works :)
>
> ...
>
> Anyway... I had hopes to get a stable release out in august. I AM very happy about the major stuff that got fixed, instead... but...
>
> Since we didn't... I now have a ton of other matters piled up. Not least of which is a pending trip to england and the eu.
Have a great trip.
>
> So for the next month I don't see how I'm going to be able to put more than a day a week into cerowrt. Tops. So I have tagged up this "release" and pushed all the baked portions of the sources to github.
Thanks a lot.
> I'm still a little dubious of the ipv6 subtrees bit….
RRUL-Testing against Toke's server shows great results, local rrul testing between osx 10.8.4 machine on sw10 to a net server running on an linux x86_64 3.10.1 machine on se00 is quite bad though (I assume I now run into the wifi issues on the macbook or the router as this is the first time I test against a machine with considerable larger bandwidth than the wlan). The rrul plots still are quite interesting, as I could nicely see anticoorelation between up and down bandwidth (shared medium)
If I get round to it I would like to re-enable fq_codel on all interfaces (now it is just running at ge00/ifb0) to see whether this can ameliorate the issue at least a bit.
Note, I enabled the log for /usr/sbin/deblaot (by editing/etc/hotplug.d/iface/00-debloat) and got the following:
root@nacktmulle:~# cat /tmp/debloat.log
fq_codel_ll
fq_codel_ll
fq_codel_ll
fq_codel_ll
root@nacktmulle:~# cat /tmp/debloat2.log
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Usage: tc [ OPTIONS ] OBJECT { COMMAND | help }
tc [-force] -batch filename
where OBJECT := { qdisc | class | filter | action | monitor }
OPTIONS := { -s[tatistics] | -d[etails] | -r[aw] | -p[retty] | -b[atch] [filename] }
Not sure whether that is new, as I never enabled the logs before. I guess I will see what causes these… (I assume an improper set of arguments to tc). And now I am trying to ind my way around debloat, but lua is totally new to me...
Best Regards & many thanks
Sebastian
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2013-09-11 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 0:28 Dave Taht
2013-09-10 5:14 ` Dave Taht
2013-09-10 9:45 ` Fred Stratton
2013-09-10 10:07 ` Fred Stratton
2013-09-12 0:16 ` Dave Taht
2013-09-12 4:27 ` Fred Stratton
2013-09-12 15:49 ` Fred Stratton
2013-09-12 15:55 ` Fred Stratton
2013-09-12 16:31 ` Fred Stratton
2013-09-12 16:41 ` Fred Stratton
2013-09-11 8:36 ` Sebastian Moeller [this message]
2013-09-12 4:10 ` 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/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=E07E6678-32FB-4A9A-A496-14CC4B83564F@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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