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] the "last" 3.6 kernel patches have landed for cerowrt....
Date: Mon, 3 Dec 2012 12:18:41 +0100	[thread overview]
Message-ID: <CAA93jw6dL+p1jLUULdJn-gBUX5pce1A9vhLKpo0zfqgdzv7hSA@mail.gmail.com> (raw)

I have been carrying around a picostation 2HP and gradually folding
back into the openwrt head build for it, all the kernel patches in
cerowrt-3.3 that were not accepted in this go-round with openwrt.

The highly specialized build for the nanostation M5 and 2HP is here.
You will need babel on to even see the device after flashing it.

http://snapon.lab.bufferbloat.net/~cero2/ubnt/3.6/3.6.8-5/

Thanks to the timely intervention of Robert Bradly, the giant set of
hacks that double ipv6 performance on this hardware are now in there.

In my stay at the university of Modena I also worked with two of their
researchers and several of their students to also fold in qfq+ and bfq
(which is used in cyanogenmod on android, among other places).

Some documentation on BFQ and QFQ+

http://algo.ing.unimo.it/people/paolo/disk_sched/
http://algo.ing.unimo.it/people/paolo/agg-sched/short-description.php

And steven walker has been busy updating packages in ceropackages...

As sort of noted in some previous emails, the course ahead for ipv6
support in userspace is a bit murky at present...

I hope to start sorting that out and to get a build of cerowrt-next
(3.6 based)... as soon as that is sorted out!

I'll be in paris, working out of the Lincs.fr lab this week, looking
into issues with torrents, however.

I have a recording (that also needs editing) of simon kelly and I
talking about futures for dnsmasq, as well as one with david woodhouse
about ADSL... in addition to the talk about queue theory history
referenced previously....

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

                 reply	other threads:[~2012-12-03 11:18 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=CAA93jw6dL+p1jLUULdJn-gBUX5pce1A9vhLKpo0zfqgdzv7hSA@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