From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id BC06221F14D for ; Fri, 27 Dec 2013 17:14:47 -0800 (PST) Received: by mail-we0-f178.google.com with SMTP id u57so8573741wes.37 for ; Fri, 27 Dec 2013 17:14:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DmE5MdV08LyOR7HmlnyiYWajwmzjaezELRsFNYL9RZw=; b=eLNzwo8kvUA6mjJqLDvpbzbNahXOJXm1sjAJnSL3uE8cGZDs12UV0lgzJtV2ZLkmRT YIKQpO/dOimQkb6p4ob6qdHHCv7Pl2DJTzWBy9XVILLu7Oz6xQQE2vQDkDFCdWplv3jd Xve5g3+o74zhX0SxBTmUJp5mWNHTPJl0QhhnrzIsJJW98i8z3eMWtd96PMplSmzzHEaY SWxhfPoK+H6hZi2wSKQl2UKVMuV8khirp0iQUOHzE7T6jAi03O3V5g+wKTjpp09dThWI 59OCXOyEfDU3m6SqVO79PRZyO/vKmJnMfGaJRe5Xb+V9wsV0ia/PZd0glh4qiHooTXG2 3tIg== MIME-Version: 1.0 X-Received: by 10.180.90.230 with SMTP id bz6mr31981897wib.17.1388193285518; Fri, 27 Dec 2013 17:14:45 -0800 (PST) Received: by 10.217.123.69 with HTTP; Fri, 27 Dec 2013 17:14:45 -0800 (PST) Received: by 10.217.123.69 with HTTP; Fri, 27 Dec 2013 17:14:45 -0800 (PST) In-Reply-To: References: <571C0EE5-DC15-4A9C-A195-A97F93A335EB@gmail.com> <52BDD08F.2000904@imap.cc> <52BDD303.8070102@imap.cc> <76A010B1-F6DB-4DF8-98A7-6F43974B72D6@gmx.de> <52BDE104.3080704@imap.cc> Date: Fri, 27 Dec 2013 17:14:45 -0800 Message-ID: From: Dave Taht To: Sebastian Moeller Content-Type: multipart/alternative; boundary=f46d043be008a9bb7b04ee8def21 Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] Fwd: Re: CeroWrt 3.10.24-8 badly bloated? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Dec 2013 01:14:49 -0000 --f46d043be008a9bb7b04ee8def21 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I note that nfq codel (which is closer to sfq in outlook than fq codel (more like drr)) might be better in fred's case. But I'd hope for his bandwidth and workload (mostly movies) the larger target will compensate for the problems he'd had. But I don't know so... In the interest of science... I would certainly like a few days subjective non benchmark testing vs a vs pie from more people. Certainly I can "feel" a difference of fq codel vs pie. (Either are massively better than current cable modems) videoconferencing, telephony, movies, games, web browsing... Anybody else willing to spend a week on pie? It is what is mandated to be in docsis 3.1 (probably with a 10ms target) On Dec 27, 2013 4:07 PM, "Sebastian Moeller" wrote: > Hi Fred, > > > On Dec 27, 2013, at 21:20 , Fred Stratton wrote: > > > I guessed input into Dangerous options was required, but was unsure of > the syntax. Quite how /etc/config/sqm is read is another matter to be > addressed over ssh. > > > > I shall paste all in one email response, for you to rearrange at the > other end. Both use simple.qos. > > > > With pie: > > > > tc -d qdisc > > qdisc fq_codel a: dev se00 root refcnt 2 limit 1000p flows 1024 quantum > 1000 target 5.0ms interval 100.0ms ecn > > qdisc htb 1: dev ge00 root refcnt 2 r2q 10 default 12 > direct_packets_stat 6 ver 3.17 > > linklayer atm overhead 18 mtu 2047 tsize 128 > > qdisc pie 110: dev ge00 parent 1:11 limit 1000p target 25000 tupdate > 30000 alpha 2 beta 20 > > qdisc pie 120: dev ge00 parent 1:12 limit 1000p target 25000 tupdate > 30000 alpha 2 beta 20 > > qdisc pie 130: dev ge00 parent 1:13 limit 1000p target 25000 tupdate > 30000 alpha 2 beta 20 > > qdisc ingress ffff: dev ge00 parent ffff:fff1 ---------------- > > qdisc htb 1: dev ifb0 root refcnt 2 r2q 10 default 12 > direct_packets_stat 0 ver 3.17 > > linklayer atm overhead 18 mtu 2047 tsize 128 > > qdisc pie 110: dev ifb0 parent 1:11 limit 1000p target 20000 tupdate > 30000 alpha 2 beta 20 ecn > > qdisc pie 120: dev ifb0 parent 1:12 limit 1000p target 20000 tupdate > 30000 alpha 2 beta 20 ecn > > qdisc pie 130: dev ifb0 parent 1:13 limit 1000p target 20000 tupdate > 30000 alpha 2 beta 20 ecn > > qdisc mq 1: dev sw10 root > > qdisc fq_codel 10: dev sw10 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev sw10 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev sw10 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev sw10 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc mq 1: dev sw00 root > > qdisc fq_codel 10: dev sw00 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev sw00 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev sw00 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev sw00 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc mq 1: dev gw00 root > > qdisc fq_codel 10: dev gw00 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev gw00 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev gw00 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev gw00 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc mq 1: dev gw10 root > > qdisc fq_codel 10: dev gw10 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev gw10 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev gw10 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev gw10 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc fq_codel a: dev pppoe-ge00 root refcnt 2 limit 1000p flows 1024 > quantum 1000 target 5.0ms interval 100.0ms ecn > > > > > > tc class show dev ge00 > > class htb 1:11 parent 1:1 leaf 110: prio 1 rate 128000bit ceil 316000bi= t > burst 1600b cburst 1599b > > class htb 1:1 root rate 950000bit ceil 950000bit burst 1599b cburst 159= 9b > > class htb 1:10 parent 1:1 prio 0 rate 950000bit ceil 950000bit burst > 1599b cburst 1599b > > class htb 1:13 parent 1:1 leaf 130: prio 3 rate 158000bit ceil 934000bi= t > burst 1599b cburst 1599b > > class htb 1:12 parent 1:1 leaf 120: prio 2 rate 158000bit ceil 934000bi= t > burst 1599b cburst 1599b > > > > with fq_codel, and 25ms target: > > > > tc -d qdisc > > qdisc fq_codel a: dev se00 root refcnt 2 limit 1000p flows 1024 quantum > 1000 target 5.0ms interval 100.0ms ecn > > qdisc htb 1: dev ge00 root refcnt 2 r2q 10 default 12 > direct_packets_stat 9 ver 3.17 > > linklayer atm overhead 18 mtu 2047 tsize 128 > > qdisc fq_codel 110: dev ge00 parent 1:11 limit 1000p flows 1024 quantum > 300 target 25.0ms interval 100.0ms > > qdisc fq_codel 120: dev ge00 parent 1:12 limit 1000p flows 1024 quantum > 300 target 25.0ms interval 100.0ms > > qdisc fq_codel 130: dev ge00 parent 1:13 limit 1000p flows 1024 quantum > 300 target 25.0ms interval 100.0ms > > Great, so this worked okay, all three fq_codels on ge00 (egress) > have an interval of 25ms, just as the Doctor (aka, Dave) ordered :). Does > this help to get fq_codel subjectively judged performance to be equal to > pie? > > Best > Sebastian > > > > > qdisc ingress ffff: dev ge00 parent ffff:fff1 ---------------- > > qdisc htb 1: dev ifb0 root refcnt 2 r2q 10 default 12 > direct_packets_stat 0 ver 3.17 > > linklayer atm overhead 18 mtu 2047 tsize 128 > > qdisc fq_codel 110: dev ifb0 parent 1:11 limit 1000p flows 1024 quantum > 500 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 120: dev ifb0 parent 1:12 limit 1000p flows 1024 quantum > 1500 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 130: dev ifb0 parent 1:13 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc mq 1: dev sw00 root > > qdisc fq_codel 10: dev sw00 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev sw00 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev sw00 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev sw00 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc mq 1: dev sw10 root > > qdisc fq_codel 10: dev sw10 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev sw10 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev sw10 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev sw10 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc mq 1: dev gw00 root > > qdisc fq_codel 10: dev gw00 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev gw00 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev gw00 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev gw00 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc mq 1: dev gw10 root > > qdisc fq_codel 10: dev gw10 parent 1:1 limit 800p flows 1024 quantum 50= 0 > target 10.0ms interval 100.0ms > > qdisc fq_codel 20: dev gw10 parent 1:2 limit 800p flows 1024 quantum 30= 0 > target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 30: dev gw10 parent 1:3 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms ecn > > qdisc fq_codel 40: dev gw10 parent 1:4 limit 1000p flows 1024 quantum > 300 target 5.0ms interval 100.0ms > > qdisc fq_codel a: dev pppoe-ge00 root refcnt 2 limit 1000p flows 1024 > quantum 1000 target 5.0ms interval 100.0ms ecn > > > > > > tc class show dev ge00 > > class htb 1:11 parent 1:1 leaf 110: prio 1 rate 128000bit ceil 316000bi= t > burst 1600b cburst 1599b > > class htb 1:1 root rate 950000bit ceil 950000bit burst 1599b cburst 159= 9b > > class htb 1:10 parent 1:1 prio 0 rate 950000bit ceil 950000bit burst > 1599b cburst 1599b > > class htb 1:13 parent 1:1 leaf 130: prio 3 rate 158000bit ceil 934000bi= t > burst 1599b cburst 1599b > > class htb 1:12 parent 1:1 leaf 120: prio 2 rate 158000bit ceil 934000bi= t > burst 1599b cburst 1599b > > class fq_codel 110:2c9 parent 110: > > class fq_codel 120:1a5 parent 120: > > class fq_codel 120:31f parent 120: > > > > > > > > On 27/12/13 19:49, Dave Taht wrote: > >> > >> Pie has a default latency target of 20ms, fq codel 5ms. (But the fq > code target matters less as the target only applies to queue building flo= ws) > >> > >> A packet takes 13ms to transit the device at 1mbit. > >> > >> There is a change to fq codel in this release that should make fiddlin= g > with target a low speeds less needed. (But might have other problems) Sti= ll > a comparison at roughly the same target vs a vs pie in your environment > would be very interesting. > >> > >> I suggested 25ms as a test (as pie never makes 20ms anyway) > >> > >> I came close to inserting a simple formula to start increasing the > target below 4mbit in this release. > >> > >> On Dec 27, 2013 11:25 AM, "Sebastian Moeller" wrote: > >> > > >> > Hi Fred, > >> > > >> > you could try to put "target 25ms" without the quotes into the > advanced egress options field in the "Queue Discipline" tab, that is > exposed after checking "Show Dangerous Configuration". I would love to he= ar > whether that worked or not (I am not able to test anything myself). Maybe > posting the output of "tc -d qdisc" and "tc class show dev ge00" would > help. Good luck=85 > >> > > >> > > >> > Best Regards > >> > Sebastian > >> > > >> > > >> > On Dec 27, 2013, at 20:20 , Fred Stratton > wrote: > >> > > >> > > I have been using pie for approximately 3 weeks. > >> > > > >> > > You are correct, in that the outbound speed is about 800 - 900 kb/= s. > >> > > > >> > > I shall try what you suggest, but do not know how to express the > target of 25 ms as a configuration option. > >> > > > >> > > > >> > > On 27/12/13 19:15, Dave Taht wrote: > >> > >> Dear fred: are you sticking with pie? I was going to suggest you > try fq codel with a target 25ms on your outbound. (You are at 800kbit or = so > as best I recall?) > >> > >> > >> > >> On Dec 27, 2013 11:10 AM, "Fred Stratton" > wrote: > >> > >> I upgraded to 3.10.24-8 on 2013-12-23. > >> > >> > >> > >> I modified /etc/fixdaemons, adding > >> > >> /etc/init.d/sqm restart > >> > >> > >> > >> input the appropriate sqm settings, transcribed from aqm > >> > >> > >> > >> rebooted > >> > >> > >> > >> and the build works very well. For ADSL2+ here, it is the best so > far. > >> > >> > >> > >> > >> > >> On 27/12/13 18:55, Dave Taht wrote: > >> > >>> A race condition appears to have crept in... > >> > >>> > >> > >>> ---------- Forwarded message ---------- > >> > >>> From: "Dave Taht" > >> > >>> Date: Dec 27, 2013 10:47 AM > >> > >>> Subject: Re: [Cerowrt-devel] CeroWrt 3.10.24-8 badly bloated? > >> > >>> To: "Richard E. Brown" > >> > >>> Cc: > >> > >>> > >> > >>> Probably didn't start sqm properly > >> > >>> > >> > >>> Restart it by hand via /etc/init.d/sqm restart > >> > >>> > >> > >>> tc -s qdisc show dev ge00 > >> > >>> > >> > >>> Should show htb and fq codel. > >> > >>> > >> > >>> On Dec 27, 2013 10:36 AM, "Rich Brown" > wrote: > >> > >>> So I screwed up my courage and replaced my 3.10.18-? firmware in > my primary router with 3.10.24-8. That version had worked well as a > secondary, so I figured, What the heck=85 Let=92s give it try. > >> > >>> > >> > >>> The result was not pretty. I set my link speeds in the SQM page, > chose the defaults for the Queue Discipline tab, and link layer to ATM wi= th > no additional overhead for my DSL link. > >> > >>> > >> > >>> Ping times to google are normally ~51-54 msec. But when I fired > up speedtest.net, they jumped to 1500-2500 msec. Is there something I > should look at before reverting? Thanks. > >> > >>> > >> > >>> Rich > >> > >>> _______________________________________________ > >> > >>> Cerowrt-devel mailing list > >> > >>> Cerowrt-devel@lists.bufferbloat.net > >> > >>> https://lists.bufferbloat.net/listinfo/cerowrt-devel > >> > >>> > >> > >>> > >> > >>> _______________________________________________ > >> > >>> Cerowrt-devel mailing list > >> > >>> > >> > >>> Cerowrt-devel@lists.bufferbloat.net > >> > >>> https://lists.bufferbloat.net/listinfo/cerowrt-devel > >> > >> > >> > > > >> > > _______________________________________________ > >> > > Cerowrt-devel mailing list > >> > > Cerowrt-devel@lists.bufferbloat.net > >> > > https://lists.bufferbloat.net/listinfo/cerowrt-devel > >> > > > > > --f46d043be008a9bb7b04ee8def21 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

I note that nfq codel (which is closer to sfq in outlook tha= n fq codel (more like drr)) might be better in fred's case. But I'd= hope for his bandwidth and workload (mostly movies) the larger target will= compensate for the problems he'd had. But I don't know so...

In the interest of science...

I would certainly like a few days subjective non benchmark t= esting vs a vs pie from more people. Certainly I can "feel" a dif= ference of fq codel vs pie.=A0 (Either are massively better than current ca= ble modems) videoconferencing, telephony, movies, games, web browsing...

Anybody else willing to spend a week on pie? It is what is m= andated to be in docsis 3.1 (probably with a 10ms target)

On Dec 27, 2013 4:07 PM, "Sebastian Moeller= " <moeller0@gmx.de> wrote= :
Hi Fred,


On Dec 27, 2013, at 21:20 , Fred Stratton <fredstratton@imap.cc> wrot= e:

> I guessed input into Dangerous options was required, but was unsure of= the syntax. =A0Quite how /etc/config/sqm is read is another matter to be a= ddressed over ssh.
>
> I shall paste all in one email response, for you to rearrange at the o= ther end. Both use simple.qos.
>
> With pie:
>
> tc -d qdisc
> qdisc fq_codel a: dev se00 root refcnt 2 limit 1000p flows 1024 quantu= m 1000 target 5.0ms interval 100.0ms ecn
> qdisc htb 1: dev ge00 root refcnt 2 r2q 10 default 12 direct_packets_s= tat 6 ver 3.17
> =A0linklayer atm overhead 18 mtu 2047 tsize 128
> qdisc pie 110: dev ge00 parent 1:11 limit 1000p target 25000 tupdate 3= 0000 alpha 2 beta 20
> qdisc pie 120: dev ge00 parent 1:12 limit 1000p target 25000 tupdate 3= 0000 alpha 2 beta 20
> qdisc pie 130: dev ge00 parent 1:13 limit 1000p target 25000 tupdate 3= 0000 alpha 2 beta 20
> qdisc ingress ffff: dev ge00 parent ffff:fff1 ----------------
> qdisc htb 1: dev ifb0 root refcnt 2 r2q 10 default 12 direct_packets_s= tat 0 ver 3.17
> =A0linklayer atm overhead 18 mtu 2047 tsize 128
> qdisc pie 110: dev ifb0 parent 1:11 limit 1000p target 20000 tupdate 3= 0000 alpha 2 beta 20 ecn
> qdisc pie 120: dev ifb0 parent 1:12 limit 1000p target 20000 tupdate 3= 0000 alpha 2 beta 20 ecn
> qdisc pie 130: dev ifb0 parent 1:13 limit 1000p target 20000 tupdate 3= 0000 alpha 2 beta 20 ecn
> qdisc mq 1: dev sw10 root
> qdisc fq_codel 10: dev sw10 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev sw10 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev sw10 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev sw10 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc mq 1: dev sw00 root
> qdisc fq_codel 10: dev sw00 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev sw00 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev sw00 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev sw00 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc mq 1: dev gw00 root
> qdisc fq_codel 10: dev gw00 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev gw00 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev gw00 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev gw00 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc mq 1: dev gw10 root
> qdisc fq_codel 10: dev gw10 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev gw10 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev gw10 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev gw10 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc fq_codel a: dev pppoe-ge00 root refcnt 2 limit 1000p flows 1024 = quantum 1000 target 5.0ms interval 100.0ms ecn
>
>
> tc class show dev ge00
> class htb 1:11 parent 1:1 leaf 110: prio 1 rate 128000bit ceil 316000b= it burst 1600b cburst 1599b
> class htb 1:1 root rate 950000bit ceil 950000bit burst 1599b cburst 15= 99b
> class htb 1:10 parent 1:1 prio 0 rate 950000bit ceil 950000bit burst 1= 599b cburst 1599b
> class htb 1:13 parent 1:1 leaf 130: prio 3 rate 158000bit ceil 934000b= it burst 1599b cburst 1599b
> class htb 1:12 parent 1:1 leaf 120: prio 2 rate 158000bit ceil 934000b= it burst 1599b cburst 1599b
>
> with fq_codel, and 25ms target:
>
> tc -d qdisc
> qdisc fq_codel a: dev se00 root refcnt 2 limit 1000p flows 1024 quantu= m 1000 target 5.0ms interval 100.0ms ecn
> qdisc htb 1: dev ge00 root refcnt 2 r2q 10 default 12 direct_packets_s= tat 9 ver 3.17
> =A0linklayer atm overhead 18 mtu 2047 tsize 128
> qdisc fq_codel 110: dev ge00 parent 1:11 limit 1000p flows 1024 quantu= m 300 target 25.0ms interval 100.0ms
> qdisc fq_codel 120: dev ge00 parent 1:12 limit 1000p flows 1024 quantu= m 300 target 25.0ms interval 100.0ms
> qdisc fq_codel 130: dev ge00 parent 1:13 limit 1000p flows 1024 quantu= m 300 target 25.0ms interval 100.0ms

=A0 =A0 =A0 =A0 Great, so this worked okay, all three fq_codels on ge00 (eg= ress) have an interval of 25ms, just as the Doctor (aka, Dave) ordered :). = Does this help to get fq_codel subjectively judged performance to be equal = to pie?

Best
=A0 =A0 =A0 =A0 Sebastian



> qdisc ingress ffff: dev ge00 parent ffff:fff1 ----------------
> qdisc htb 1: dev ifb0 root refcnt 2 r2q 10 default 12 direct_packets_s= tat 0 ver 3.17
> =A0linklayer atm overhead 18 mtu 2047 tsize 128
> qdisc fq_codel 110: dev ifb0 parent 1:11 limit 1000p flows 1024 quantu= m 500 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 120: dev ifb0 parent 1:12 limit 1000p flows 1024 quantu= m 1500 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 130: dev ifb0 parent 1:13 limit 1000p flows 1024 quantu= m 300 target 5.0ms interval 100.0ms ecn
> qdisc mq 1: dev sw00 root
> qdisc fq_codel 10: dev sw00 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev sw00 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev sw00 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev sw00 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc mq 1: dev sw10 root
> qdisc fq_codel 10: dev sw10 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev sw10 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev sw10 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev sw10 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc mq 1: dev gw00 root
> qdisc fq_codel 10: dev gw00 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev gw00 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev gw00 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev gw00 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc mq 1: dev gw10 root
> qdisc fq_codel 10: dev gw10 parent 1:1 limit 800p flows 1024 quantum 5= 00 target 10.0ms interval 100.0ms
> qdisc fq_codel 20: dev gw10 parent 1:2 limit 800p flows 1024 quantum 3= 00 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 30: dev gw10 parent 1:3 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms ecn
> qdisc fq_codel 40: dev gw10 parent 1:4 limit 1000p flows 1024 quantum = 300 target 5.0ms interval 100.0ms
> qdisc fq_codel a: dev pppoe-ge00 root refcnt 2 limit 1000p flows 1024 = quantum 1000 target 5.0ms interval 100.0ms ecn
>
>
> tc class show dev ge00
> class htb 1:11 parent 1:1 leaf 110: prio 1 rate 128000bit ceil 316000b= it burst 1600b cburst 1599b
> class htb 1:1 root rate 950000bit ceil 950000bit burst 1599b cburst 15= 99b
> class htb 1:10 parent 1:1 prio 0 rate 950000bit ceil 950000bit burst 1= 599b cburst 1599b
> class htb 1:13 parent 1:1 leaf 130: prio 3 rate 158000bit ceil 934000b= it burst 1599b cburst 1599b
> class htb 1:12 parent 1:1 leaf 120: prio 2 rate 158000bit ceil 934000b= it burst 1599b cburst 1599b
> class fq_codel 110:2c9 parent 110:
> class fq_codel 120:1a5 parent 120:
> class fq_codel 120:31f parent 120:
>
>
>
> On 27/12/13 19:49, Dave Taht wrote:
>>
>> Pie has a default latency target of 20ms, fq codel 5ms. (But the f= q code target matters less as the target only applies to queue building flo= ws)
>>
>> A packet takes 13ms to transit the device at 1mbit.
>>
>> There is a change to fq codel in this release that should make fid= dling with target a low speeds less needed. (But might have other problems)= Still a comparison at roughly the same target vs a vs pie in your environm= ent would be very interesting.
>>
>> I suggested 25ms as a test (as pie never makes 20ms anyway)
>>
>> I came close to inserting a simple formula to start increasing the= target below 4mbit in this release.
>>
>> On Dec 27, 2013 11:25 AM, "Sebastian Moeller" <moeller0@gmx.de> wrote:
>> >
>> > Hi Fred,
>> >
>> > you could try to put "target 25ms" without the quot= es into the advanced egress options field in the "Queue Discipline&quo= t; tab, that is exposed after checking "Show Dangerous Configuration&q= uot;. I would love to hear whether that worked or not (I am not able to tes= t anything myself). Maybe posting the output of "tc -d qdisc" and= "tc class show dev ge00" would help. Good luck=85
>> >
>> >
>> > Best Regards
>> > =A0 =A0 =A0 =A0 Sebastian
>> >
>> >
>> > On Dec 27, 2013, at 20:20 , Fred Stratton <fredstratton@im= ap.cc> wrote:
>> >
>> > > I have been using pie for approximately 3 weeks.
>> > >
>> > > You are correct, in that the outbound speed is about 800= - 900 kb/s.
>> > >
>> > > I shall try what you suggest, but do not know how to exp= ress the target of 25 ms as a configuration option.
>> > >
>> > >
>> > > On 27/12/13 19:15, Dave Taht wrote:
>> > >> Dear fred: are you sticking with pie? I was going to= suggest you try fq codel with a target 25ms on your outbound. (You are at = 800kbit or so as best I recall?)
>> > >>
>> > >> On Dec 27, 2013 11:10 AM, "Fred Stratton" = <fredstratton@imap.cc> wrote:
>> > >> I upgraded to 3.10.24-8 on 2013-12-23.
>> > >>
>> > >> I modified /etc/fixdaemons, adding
>> > >> /etc/init.d/sqm restart
>> > >>
>> > >> input the appropriate sqm settings, transcribed from= aqm
>> > >>
>> > >> rebooted
>> > >>
>> > >> and the build works very well. For ADSL2+ here, it i= s the best so far.
>> > >>
>> > >>
>> > >> On 27/12/13 18:55, Dave Taht wrote:
>> > >>> A race condition appears to have crept in...
>> > >>>
>> > >>> ---------- Forwarded message ----------
>> > >>> From: "Dave Taht" <dave.taht@gmail.com>
>> > >>> Date: Dec 27, 2013 10:47 AM
>> > >>> Subject: Re: [Cerowrt-devel] CeroWrt 3.10.24-8 b= adly bloated?
>> > >>> To: "Richard E. Brown" <richb.hanover@gmail.com>
>> > >>> Cc:
>> > >>>
>> > >>> Probably didn't start sqm properly
>> > >>>
>> > >>> Restart it by hand via /etc/init.d/sqm restart >> > >>>
>> > >>> tc -s qdisc show dev ge00
>> > >>>
>> > >>> Should show htb and fq codel.
>> > >>>
>> > >>> On Dec 27, 2013 10:36 AM, "Rich Brown"= <richb.hanover@gmail.com= > wrote:
>> > >>> So I screwed up my courage and replaced my 3.10.= 18-? firmware in my primary router with 3.10.24-8. That version had worked = well as a secondary, so I figured, What the heck=85 Let=92s give it try. >> > >>>
>> > >>> The result was not pretty. I set my link speeds = in the SQM page, chose the defaults for the Queue Discipline tab, and link = layer to ATM with no additional overhead for my DSL link.
>> > >>>
>> > >>> Ping times to google are normally ~51-54 msec. B= ut when I fired up speed= test.net, they jumped to 1500-2500 msec. Is there something I should lo= ok at before reverting? Thanks.
>> > >>>
>> > >>> Rich
>> > >>> _______________________________________________<= br> >> > >>> Cerowrt-devel mailing list
>> > >>> Cerowrt-devel@lists.bufferbloat.net
>> > >>> https://lists.bufferbloat.net/listinfo/c= erowrt-devel
>> > >>>
>> > >>>
>> > >>> _______________________________________________<= br> >> > >>> Cerowrt-devel mailing list
>> > >>>
>> > >>> Cerowrt-devel@lists.bufferbloat.net
>> > >>> https://lists.bufferbloat.net/listinfo/c= erowrt-devel
>> > >>
>> > >
>> > > _______________________________________________
>> > > Cerowrt-devel mailing list
>> > > C= erowrt-devel@lists.bufferbloat.net
>> > > https://lists.bufferbloat.net/listinfo/cerowrt-d= evel
>> >
>

--f46d043be008a9bb7b04ee8def21--