Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] a note on 'debloat'
Date: Thu, 23 Feb 2012 16:12:43 +0000	[thread overview]
Message-ID: <CAA93jw7SzQhdMmvVqQE6VcT-+hWYmXd2eG=HKg+r0J6W3eP5xA@mail.gmail.com> (raw)

I note that I have been analyzing various aqm models using a lua
script called 'debloat'

The git repo for the debloat script and some of the test data is at:

https://github.com/dtaht/deBloat

in the src/debloat script.

The nice thing about debloat is that it works on a 'normal' linux box
running 3.3 with BQL and QFQ enabled,
as well as on openwrt/cerowrt.

It's much easier to prototype AQM stuff on non-embedded hardware.

Also I run the new sfqred code by default on all interfaces on my own
gear and the benefit is often noticeable in normal use.

It wasn't until recently (the underlying kernel code had to work
first!) that I started adding htb and hfsc support to it, so much of
that work is incomplete, hard-coded, or just plain buggy.

But I do find working with lua much better for handling complex stuff
that shell scripts weren't doing for me.

A brief intro on how to use it is in the usage message, from a
code-reading standpoint, those unfamiliar with the language (I started
writing this in late december having had no exposure to lua before),
can start
from the bottom  and read up....

basically, though

IFACE=wlan0 QMODEL=sfqred ./debloat
IFACE=eth0 QMODEL=qfq ./debloat

etc.

from an htb front, I've had the most success with the htb_sfq_red
model, which is currently
hard coded for 4Mbits...


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

                 reply	other threads:[~2012-02-23 16:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAA93jw7SzQhdMmvVqQE6VcT-+hWYmXd2eG=HKg+r0J6W3eP5xA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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