From: Jim Gettys <jg@freedesktop.org>
To: bloat-devel@lists.bufferbloat.net
Subject: Debloat testing2.6.39-rc4 kernel...
Date: Wed, 20 Apr 2011 20:22:55 -0400 [thread overview]
Message-ID: <4DAF78DF.2010203@freedesktop.org> (raw)
I've built (and am running) John Linville's latest debloat-testing
2.6.39-rc4 kernel. It seems to behave alot better than the 2.6.38 kernel
did for me on the Intel iwlagn driver, given (all of) about 10 minutes
of testing. We haven't tried to play with SFB yet; we've mostly been
router hacking.
I put the packages Dave and I are running (64bit Ubuntu 10.10) on
http://mirrors.bufferbloat.net/Builds/
I also did a quick script for setting the wireless txqueuelen to
something more reasonable at driver up time; you can find it at:
http://www.bufferbloat.net/projects/bloat/wiki/Wlan_script; at the
moment, it's set to only 32 packets and my latency under load is staying
somewhat reasonable with at least some decent throughput. But given 10
minutes of smoke testing... Dead puppies are possible. No warranties,
express or implied...
I documented this in:
http://www.bufferbloat.net/projects/bloat/wiki/Linux_Tips
If people have the ability to set up and Ubuntu PPA, or can run packages
through RH's build system (Koji, iirc), that would be good, so that
people who want to test don't necessarily have to build from source all
the time. It would be really good to get debloat testing kernel
packages built automatically on an ongoing basis from John's tree,one
way or the other. The other way to automate this is by using the server
we have now that can build kernels in finite time; we can set up VM's on
to build them. But that is a lot more on-going build system maintenance
So I'm a fan of using the upstream distro build systems for this if we
can; we have lots of build work to do for the work that is underway to
debloat the WNDR3700's running OpenWRT. Volunteers more than welcome
for either/both.
- Jim
next reply other threads:[~2011-04-22 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 0:22 Jim Gettys [this message]
2011-04-21 9:39 Jim Gettys
2011-04-21 22:09 Jim Gettys
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=4DAF78DF.2010203@freedesktop.org \
--to=jg@freedesktop.org \
--cc=bloat-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