From: Jonathan Morton <chromatix99@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
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 23:45:07 +0300 [thread overview]
Message-ID: <CAJq5cE3QpOm95xGCBrG1OVDa6OMXJmjLardVcyprBxhY39LsgQ@mail.gmail.com> (raw)
In-Reply-To: <14098.1438374207@sandelman.ca>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
There is some subtlety of terminology here...
Fq_codel has many queues, but they are not a priori assigned as "low
latency" or otherwise. There is a dynamic sense of whether each queue is
handling sparse or bulk traffic, with the sparse queues being serviced
first. This is a type of priority queuing which is difficult to game (and
completely ignores Diffserv).
Cake does the same thing, and additionally divides the queue using
Diffserv. Etcetera.
Both fq_codel and cake deliver one packet at a time. This is a feature of
the qdisc API within the kernel. They have no visibility of what
aggregation might be happening at the hardware level, only that the driver
is requesting a packet.
Wi-Fi hardware implementing 802.11e tends to have four queues, each of
which is a dumb FIFO, and services only one of them per TXOP (probably the
highest priority one). It doesn't even do the "naive" thing you mention -
which goes some way to illustrate the point of view of the typical hardware
engineer.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1151 bytes --]
next prev parent reply other threads:[~2015-07-31 20:45 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
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 [this message]
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=CAJq5cE3QpOm95xGCBrG1OVDa6OMXJmjLardVcyprBxhY39LsgQ@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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