From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: codel@lists.bufferbloat.net
Subject: [Codel] what am i doing wrong? why isn't codel working?
Date: Tue, 24 Jun 2014 08:37:15 -0400 [thread overview]
Message-ID: <1403613435.3478.727.camel@pc.interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Hi all,
I've upgraded my router to OpenWRT Breaker Barrier r41163 which has
kernel 3.10.36 in it. I was pleased to see that codel appears (to my
very newbie eyes) to be default on what should be the
"fast->slow" (where bufferbloat happens) interfaces:
qdisc fq_codel 0: dev eth0 root refcnt 2 limit 1024p flows 1024 quantum 300 target 5.0ms interval 100.0ms ecn
qdisc mq 0: dev wlan1 root
qdisc mq 0: dev wlan0 root
qdisc fq_codel 0: dev pppoe-wan1 root refcnt 2 limit 1024p flows 1024 quantum 300 target 5.0ms interval 100.0ms ecn
qdisc fq_codel 0: dev tun0 root refcnt 2 limit 1024p flows 1024 quantum 300 target 5.0ms interval 100.0ms ecn
So first thing to notice is that this router has two WAN interfaces but
only one of them (pppoe-wan1) has had codel applied. The other WAN
interface (eth0.2) is not even listed.
So off I go to experiment with the WAN interface that does have codel
applied...
So I do the saturate-and-ping test through pppoe-wan1 and ping times go
from ~12ms to ~1200ms, while saturating the upstream so clearly codel is
not working there.
What am I doing wrong?
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2014-06-24 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 12:37 Brian J. Murrell [this message]
2014-06-24 13:22 Brian J. Murrell
2014-06-24 16:07 ` Stephen Hemminger
2014-06-24 16:11 ` Eric Dumazet
2014-06-24 16:26 ` Dave Taht
2014-06-24 17:29 ` Brian J. Murrell
2014-06-24 18:20 ` 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=1403613435.3478.727.camel@pc.interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=codel@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