From: Dave Taht <dave.taht@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Nathaniel J. Smith" <njs@pobox.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] debloat-testing tree rebased, some patches dropped
Date: Wed, 30 Mar 2011 16:06:49 -0400 [thread overview]
Message-ID: <AANLkTi=LmzmwFgMV1a+KRZpUW7xE+TjCMUHYx5vXbNaV@mail.gmail.com> (raw)
In-Reply-To: <20110330191156.GC2520@tuxdriver.com>
On Wed, Mar 30, 2011 at 3:11 PM, John W. Linville
<linville@tuxdriver.com> wrote:
> FYI...
>
> I have rebased the wireless-testing tree on 2.6.39-rc1. As previously
> stated, I plan to track the -rc and final releases, rebasing on
> each -rc1. The rebase is a little ugly/painful, but it is a good
> way to avoid building-up too much cruft in a tree that isn't going
> to be pulled by Linus anyway.
>
> I dropped the patches that were already present in 2.6.39-rc1, along
> with the ones that had gotten reverted in debloat-testing already.
> I also dropped Nathaniel's iwlwifi patches, as the iwlwifi/iwlegacy
> split made preserving them a little awkward. Maybe Nathaniel can
> post revisions?
>
> Anyway, that doesn't leave much -- a couple of ugly patches from Dave
> and me, neither likely to make it upstream. They are looking a bit
> lonely in there...surely someone has some experimental stuff that
> craves an audience of testers?
I'd like to point out that the really good patches (the ECN fix, SFB,
CHOKe) landed upstream so fast that a stay in debloat-testing was
almost not necessary.
Highest on my personal lists of "would likes":
1) I would certainly like to see the AQMs above thoroughly tested with
some new shaper scripts now that they are in the rc1 kernel!
(did those patches get backported into openwrt?)
As for moving further with debloat-testing:
JG will be back from Europe April 3rd-ish.
I'm traveling up the East Coast starting sunday, making stops at
gatech, washington, DC, Philly, Boston, and Illinois, before getting
to California in late April.
So I'm trying to assemble a build system (for multiple distros) that
works before hacking on kernels any more, personally. It's far better
to light up the new server (huchra) for 13 minutes than making my
laptop glow for 2 hours... but it's not quite there yet. Friday, I
hope? With a little help??
Technically I'm trying to get a grip on the "day in the life of a TCP
stream", to see where latencies are introduced across the stack.
Patches I'd love to see:
IWL patch
More work on instrumenting eBDP, Wireless, Ath9k, A USB wireless stick...
Support for per-device TCP algorithms.
TCP-FIT, anyone?
I was under the impression there were several other packet schedulers
in the works
and there was some iptables connection tracking work that seemed interesting
>
> Let me know if there are problems!
>
> John
> --
> John W. Linville Someday the world will need a hero, and you
> linville@tuxdriver.com might be all we have. Be ready.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next prev parent reply other threads:[~2011-03-30 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 19:11 John W. Linville
2011-03-30 20:06 ` Dave Taht [this message]
2011-03-30 20:19 ` Eric Dumazet
2011-03-30 20:32 ` Jonathan Morton
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=LmzmwFgMV1a+KRZpUW7xE+TjCMUHYx5vXbNaV@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=linville@tuxdriver.com \
--cc=njs@pobox.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