From: "John W. Linville" <linville@tuxdriver.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: linux-wireless@vger.kernel.org, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat bug 216 could use some eyeballs badly
Date: Mon, 1 Aug 2011 09:30:45 -0400 [thread overview]
Message-ID: <20110801133044.GA28112@tuxdriver.com> (raw)
In-Reply-To: <CAA93jw5jPe__jjxo5PMUm5S6ffcyapmqzXgXqtNX4Cd0ToE7vA@mail.gmail.com>
On Mon, Aug 01, 2011 at 06:06:43AM -0600, Dave Taht wrote:
> If anyone can spare some eyeballs for the discussion of wireless-n AMPDUs
> and their interaction with bufferbloat, and groks TCP's behavior and/or
> wireless's behavior, I'd appreciate some comment on:
>
> http://www.bufferbloat.net/issues/216
>
> Losing SOME appropriate packets, somewhere in the wireless stack, is
> necessary.
It seems appropriate to Cc: linux-wireless@vger.kernel.org for this...
--
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-08-01 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 12:06 Dave Taht
2011-08-01 13:30 ` John W. Linville [this message]
2011-08-01 19:44 ` Simon Barber
2011-08-01 20:19 [Bloat] bufferbloat bug [#216] " 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
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=20110801133044.GA28112@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=linux-wireless@vger.kernel.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