From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: make-wifi-fast@lists.bufferbloat.net,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [tsvwg] Comments on draft-szigeti-tsvwg-ieee-802-11e
Date: Fri, 31 Jul 2015 00:56:23 +0300 [thread overview]
Message-ID: <CAJq5cE0ShGs43O=BBNH5WWHPxaJq2TJsFGs06VTpgdUmB4x06w@mail.gmail.com> (raw)
In-Reply-To: <5CC1DC90-DFAF-4A4D-8204-16CD4E20D6E3@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Hardware people tend to think in terms of simple priority queues, much like
old fashioned military communications (see the original IP precedence
spec). Higher priority thus gets higher throughput as well as lower latency.
I note also that in 802.11e, leftover space in a TXOP can't be (or at least
generally isn't) used opportunistically for traffic from another class,
because the four queues are so rigidly separated.
I think the hardware people are shortsighted in this respect. It's so easy
to game simple priority queues when there's no filter on the field
controlling it. That's why cake's Diffserv layer works the way it does. And
if I ever get the chance to do a Wi-Fi specific version, I'll avoid both of
the above problems.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 860 bytes --]
next prev parent reply other threads:[~2015-07-30 21:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E9C29602-7F1D-43AD-980C-050B58FA0AC6@iii.ca>
2015-07-23 6:48 ` [Cerowrt-devel] Fwd: " Dave Taht
2015-07-23 7:44 ` Jonathan Morton
2015-07-23 7:49 ` Alan Jenkins
2015-07-24 10:38 ` [Cerowrt-devel] [Make-wifi-fast] " Sebastian Moeller
2015-07-30 20:29 ` [Cerowrt-devel] " Jonathan Morton
2015-07-30 21:35 ` [Cerowrt-devel] [Make-wifi-fast] " Sebastian Moeller
2015-07-30 21:56 ` Jonathan Morton [this message]
2015-07-31 3:27 ` Sebastian Moeller
2015-07-31 16:47 ` dpreed
2015-07-31 17:04 ` Jonathan Morton
2015-07-31 20:23 ` Michael Richardson
2015-07-31 20:45 ` Jonathan Morton
2015-08-03 15:44 ` dpreed
2015-08-03 16:14 ` David Lang
2015-08-03 23:37 ` dpreed
2015-08-03 23:52 ` Jonathan Morton
2015-08-04 0:13 ` David Lang
2015-08-04 16:55 ` dpreed
2015-08-07 8:28 ` Mikael Abrahamsson
2015-08-07 13:22 ` Rich Brown
2015-08-07 13:28 ` Jonathan Morton
2015-08-07 17:35 ` Rich Brown
2015-08-08 14:25 ` Simon Barber
2015-08-07 20:03 ` David Lang
2015-08-07 21:46 ` dpreed
2015-08-07 22:31 ` David Lang
2015-08-08 20:46 ` dpreed
2015-08-08 23:23 ` David Lang
2015-08-09 19:31 ` Jonathan Morton
2015-08-09 21:50 ` David Lang
2015-08-10 5:39 ` Mikael Abrahamsson
2015-08-13 21:48 ` David Lang
2015-08-13 22:14 ` Jonathan Morton
2015-08-13 22:25 ` David Lang
2015-08-13 22:30 ` Jonathan Morton
2015-08-09 22:09 ` David Lang
2015-08-10 13:48 ` Simon Barber
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJq5cE0ShGs43O=BBNH5WWHPxaJq2TJsFGs06VTpgdUmB4x06w@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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