From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] bufferbloat bug 216 could use some eyeballs badly
Date: Mon, 1 Aug 2011 06:06:43 -0600 [thread overview]
Message-ID: <CAA93jw5jPe__jjxo5PMUm5S6ffcyapmqzXgXqtNX4Cd0ToE7vA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
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.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 577 bytes --]
next reply other threads:[~2011-08-01 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 12:06 Dave Taht [this message]
2011-08-01 13:30 ` John W. Linville
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=CAA93jw5jPe__jjxo5PMUm5S6ffcyapmqzXgXqtNX4Cd0ToE7vA@mail.gmail.com \
--to=dave.taht@gmail.com \
--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