From: Jonathan Morton <chromatix99@gmail.com>
To: David Lang <david@lang.hm>
Cc: make-wifi-fast@lists.bufferbloat.net,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] [tsvwg] Comments on draft-szigeti-tsvwg-ieee-802-11e
Date: Sun, 9 Aug 2015 22:31:16 +0300 [thread overview]
Message-ID: <CAJq5cE210BeKF9HrbUd2Rj1-=imWcFXUPz8rumXu1aKxiiHRtw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1508081619140.2141@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
The question of whether to aggregate under congested conditions is
controversial, probably because it depends on complex conditions. There
are arguments both for and against.
It may be worth considering it as a risk/reward tradeoff. Given N packets
(which for brevity I'll assume are equal MTU sized), the reward is
obviously proportional to N. Risk however is calculated as probability *
consequence.
Assuming all packets in the aggregate are lost on collision, the risk of
collision scales with L*N, where L is N plus the overhead of the TXOP.
Under that argument, usually you should not aggregate if the probability of
collision is high.
However, if only one packet is lost due to collision with, for example, a
small RTS probe which is not answered, the risk scales with L, which is
sublinear compared to the reward relative to the amount of aggregation
(especially at high data rates where the TXOP overhead is substantial).
Under this assumption, aggregation is usually profitable even with a high
collision probability, and results in overall higher efficiency whether or
not collisions are likely.
This is the difference between the typical 802.11n situation (one checksum
per aggregate) and the mandatory 802.11ac capability of a checksum per
packet. As long as you also employ RTS/CTS when appropriate, the
possibility of collisions is no longer a reason to avoid aggregating.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1535 bytes --]
next prev parent reply other threads:[~2015-08-09 19:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E9C29602-7F1D-43AD-980C-050B58FA0AC6@iii.ca>
2015-07-23 6:48 ` [Make-wifi-fast] Fwd: " Dave Taht
2015-07-23 7:44 ` [Make-wifi-fast] [Cerowrt-devel] " Jonathan Morton
2015-07-23 7:49 ` Alan Jenkins
2015-07-24 10:38 ` Sebastian Moeller
2015-07-30 20:29 ` [Make-wifi-fast] [Cerowrt-devel] " Jonathan Morton
2015-07-30 21:35 ` 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
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-04 3:20 ` Simon Barber
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 [this message]
2015-08-09 20:27 ` Simon Barber
2015-08-09 21:43 ` David Lang
2015-08-10 14:00 ` Simon Barber
2015-08-10 18:44 ` David Lang
2015-08-10 19:21 ` Jonathan Morton
2015-08-10 21:18 ` Simon Barber
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
2015-08-04 3:26 ` Simon Barber
2015-08-04 3:16 ` 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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJq5cE210BeKF9HrbUd2Rj1-=imWcFXUPz8rumXu1aKxiiHRtw@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--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