From: Michael Richardson <mcr@sandelman.ca>
To: Jonathan Morton <chromatix99@gmail.com>
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 16:23:27 -0400 [thread overview]
Message-ID: <14098.1438374207@sandelman.ca> (raw)
In-Reply-To: <CAJq5cE1CmHjhkmG-_c3yLEX-uViTMk7OVf9trS+gEB6Djpw4gQ@mail.gmail.com>
Jonathan Morton <chromatix99@gmail.com> wrote:
>> I think that is achievable, *even if there is a WiFi network in the
> middle*, by thinking about the fact that the shared airwaves in a WiFi
> network behaves like a single link, so all the queues on individual
> stations are really *one queue*, and that the optimal behavior of that
> link will be achieved if there is at most one packet queued at a time.
> I agree that queues should be kept short in general. However I don't
> think single packet queues are achievable in the general case.
> The general case includes Wi-Fi networks, whose TXOP overhead is so
> ruinously heavy that sending single MTU sized packets is
> inefficient. Aggregating multiple packets into one TXOP requires those
> several packets to be present in the buffer at that moment.
Agreed... if one has a minimum of two queues (and *fq-codel has at least that
many), why isn't the naive method of:
1) send everything from the low-latency queue
2) send the other stuff until the TXOP is full
enough? codel will keep the queues short.
The key thing I think, is that the markings (1)/(2) above be passed along
through all "subqueues"...
next prev parent reply other threads:[~2015-07-31 20:31 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 [this message]
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=14098.1438374207@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=make-wifi-fast@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