From: "John W. Linville" <linville@tuxdriver.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: what I think is wrong with eBDP in debloat-testing
Date: Mon, 7 Nov 2011 14:25:17 -0500 [thread overview]
Message-ID: <20111107192517.GH2798@tuxdriver.com> (raw)
In-Reply-To: <CAA93jw4+mtDQgRpVD-082Xs0gTWobTg8ZLPBBNa7yUUzJJ-fHg@mail.gmail.com>
On Mon, Nov 07, 2011 at 08:10:57PM +0100, Dave Taht wrote:
> John was right when he wrote in the initial announcement:
>
> "This version runs separate instances of the algorithm for each WMM
> queue -- I reckon that makes sense. "
>
> and it doesn't.
>
> "I still ignore HT aggregation, as I'm pretty sure I don't understand
> how it really effects the issue."
>
> Messes it up completely.
So, can I drop that patch from debloat-testing now? :-)
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-11-07 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 19:10 Dave Taht
2011-11-07 19:22 ` Dave Taht
2011-11-07 19:25 ` John W. Linville [this message]
2011-11-07 19:56 ` Dave Taht
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=20111107192517.GH2798@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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