Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	cake <cake@lists.bufferbloat.net>
Cc: Jonathan Morton <chromatix99@gmail.com>
Subject: Re: [Cerowrt-devel] Latest build test - new sqm-scripts seem to work; "cake overhead 40" [still] didn't
Date: Sat, 20 Jun 2015 11:55:48 +0100	[thread overview]
Message-ID: <CANmMgnEH8cmvu2zTMq48W47q2L=1O98VXMi44cqhswfc5X4xGQ@mail.gmail.com> (raw)

On 19/06/2015, Dave Taht <dave.taht@gmail.com> wrote:
> Fresh bits! Get your fresh bits here! (totally untested)
>
> http://snapon.lab.bufferbloat.net/~cero3/lupin/ar71xx/

Good news: it lives!  Yum, fresh bits.

So now I can update and install packages.  Including tc-adv.  It looks
like it was overriding tc already though.

Bad news: I still can't set cake's overhead option (sticks at 0).

# tc -V
tc utility, iproute2-ss4.1.0-git-1-openwrt

# tc qdisc del dev pppoe-wan root
# tc qdisc |grep "dev pppoe-wan"
qdisc fq_codel 0: dev pppoe-wan root refcnt 2 limit 1024p flows 1024
quantum 300 target 5.0ms interval 100.0ms ecn
qdisc ingress ffff: dev pppoe-wan parent ffff:fff1 ----------------

# tc qdisc add dev pppoe-wan root cake bandwidth 970Kbit
besteffort flows atm  overhead 40

# tc qdisc |grep "dev pppoe-wan"
qdisc cake 800d: dev pppoe-wan root refcnt 2 bandwidth 970Kbit
besteffort flows atm overhead 0
qdisc ingress ffff: dev pppoe-wan parent ffff:fff1 ----------------

Alan

             reply	other threads:[~2015-06-20 10:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20 10:55 Alan Jenkins [this message]
2015-06-20 11:00 ` Jonathan Morton
2015-06-20 11:54   ` Alan Jenkins
2015-06-20 12:46     ` Jonathan Morton
2015-06-20 12:48       ` 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='CANmMgnEH8cmvu2zTMq48W47q2L=1O98VXMi44cqhswfc5X4xGQ@mail.gmail.com' \
    --to=alan.christopher.jenkins@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@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