CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] what am i doing wrong? why isn't codel working?
Date: Tue, 24 Jun 2014 09:26:22 -0700	[thread overview]
Message-ID: <CAA93jw4X4hFT5+sO0AZ-Rb22CGg8Gb676kEuemNayE6abaUyoQ@mail.gmail.com> (raw)
In-Reply-To: <1403616175.3478.731.camel@pc.interlinx.bc.ca>

Well, if your provided rate is different from line rate on the up or
down, you need to apply a rate shaper to the interface first, not just
fq_codel alone. You have to make your device be the bottleneck in
order to have control of the queue.

openwrt has the qos-scripts and luci-app-qos packages

OR

cerowrt has the sqm-scripts and luci-app-sqm packages (and these
install on top of regular openwrt)

http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_SQM_for_CeroWrt_310

A simple example of how htb is used in the above

http://wiki.gentoo.org/wiki/Traffic_shaping

On Tue, Jun 24, 2014 at 6:22 AM, Brian J. Murrell <brian@interlinx.bc.ca> wrote:
> 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.
>
>
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  parent reply	other threads:[~2014-06-24 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2014-06-24 17:29   ` Brian J. Murrell
2014-06-24 18:20     ` Dave Taht
  -- strict thread matches above, loose matches on Subject: below --
2014-06-24 12:37 Brian J. Murrell

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=CAA93jw4X4hFT5+sO0AZ-Rb22CGg8Gb676kEuemNayE6abaUyoQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=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