From: Dave Taht <dave.taht@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat-devel@lists.bufferbloat.net
Subject: Re: I put up Ubuntu 10.10 final amd64 debloat-testing packages...
Date: Fri, 20 May 2011 14:34:44 -0600 [thread overview]
Message-ID: <BANLkTinpS+sz7JbK5LJ4px17fk1jjGvjEQ@mail.gmail.com> (raw)
In-Reply-To: <4DD6CD83.4020007@freedesktop.org>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
On Fri, May 20, 2011 at 2:22 PM, Jim Gettys <jg@freedesktop.org> wrote:
> They can be found in
> http://mirrors.bufferbloat.net/Builds/
>
> I've been running this for about two hours. No serious testing has been
> done, and certainly no warranty. No kittens have died as yet.
>
In order to test tc + SFB fully, iproute2 needs to be released for 2.6.39.
http://devresources.linuxfoundation.org/dev/iproute2/download/
There is the development branch of iproute2 containing the SFB and CHOKe
stuff in the 'net-next' branch of the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
which contains that code.
So far as I know the 2.6.39 kernel contains the following
interesting-to-debloaters patches.
SFB, Choke packet schedulers
Fixes to the pfifo_fast qdisc to "do the right thing" for ECN enabled
packets
Fixes for ECN with IPv6, which was totally borked before. (I don't know if
this patch made it, actually)
The current releases of capetown/cerowrt, nearly final, also have all this
stuff backported to 2.6.37.6. These openwrt releases enable RED on the wired
wan interface. Theoretically.
Have fun hacking!
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1927 bytes --]
prev parent reply other threads:[~2011-05-20 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 20:22 Jim Gettys
2011-05-20 20:34 ` Dave Taht [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinpS+sz7JbK5LJ4px17fk1jjGvjEQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=jg@freedesktop.org \
/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