From: Simon Barber <simon@superduper.net>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] some (very good) preliminary results from fiddling with byte queue limits on 100Mbit ethernet
Date: Mon, 21 Nov 2011 21:36:27 -0800 [thread overview]
Message-ID: <4ECB34DB.30609@superduper.net> (raw)
In-Reply-To: <20111121150857.GA7153@tuxdriver.com>
I'm running something called debloat-testing from the Ubuntu kernel PPA
on my laptop.
Simon
On 11/21/2011 07:08 AM, John W. Linville wrote:
> On Sat, Nov 19, 2011 at 09:33:49PM +0100, Dave Taht wrote:
>
>> So I extracted the current set of BQL related patches from the
>> debloat-testing kernel and applied them to a recent linus-head
>> (3.2-rc2 + a little)
>> (they are at: http://www.teklibre.com/~d/tnq )
>
> FWIW, debloat-testing literally is 3.2-rc2 + the BQL patches. I hope
> you didn't spend too much time recreating that!
>
> I'm coming to the conclusion that maintaining debloat-testing is
> largely a waste of time. Does anyone (besides maybe jg) actually
> run it?
>
> John
prev parent reply other threads:[~2011-11-22 5:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:33 Dave Taht
2011-11-19 21:53 ` Tom Herbert
2011-11-19 22:47 ` Dave Taht
2011-11-21 15:08 ` John W. Linville
2011-11-22 5:36 ` Simon Barber [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
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=4ECB34DB.30609@superduper.net \
--to=simon@superduper.net \
--cc=bloat@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