Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] [tsvwg] Comments on draft-szigeti-tsvwg-ieee-802-11e
Date: Mon, 03 Aug 2015 20:20:55 -0700	[thread overview]
Message-ID: <55C02F97.2090601@superduper.net> (raw)
In-Reply-To: <CAJq5cE1CmHjhkmG-_c3yLEX-uViTMk7OVf9trS+gEB6Djpw4gQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]

Indeed - to get maximum performance with WiFi you must form large 
aggregates. They are limited to 5.3ms of data, which is a theoretical 
4MBytes of data for 11ac radios. (8x8, MCS9). In practice, today it's 
very rare to see > 3x3 and MCS8 or 9, so somewhere between 1.5 and 
2MBytes of data in an aggregate. You need sufficient queues to form 
these aggregates, or performance is very poor.

Simon

On 7/31/2015 10:04 AM, Jonathan Morton 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.
>
> The general case includes links which vary in throughput frequently, 
> perhaps on shorter timescales than an RTT, so either packets must be 
> buffered or capacity is left unused. This also happens to include 
> Wi-Fi, but could easily include a standard wired link whose competing 
> load varies.
>
> The endpoints do not have and do not receive sufficient information in 
> sufficient time to reliably make packets arrive at nodes just in time 
> to be transmitted. Not even with ECN, not even with the wet dreams of 
> the DCTCP folks, and not even with ELR (though ELR should be able to 
> make it happen under steady conditions, there are still transient 
> conditions in the general case).
>
> - Jonathan Morton
>
>
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast


[-- Attachment #2: Type: text/html, Size: 3071 bytes --]

  parent reply	other threads:[~2015-08-04  3:20 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 [this message]
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 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=55C02F97.2090601@superduper.net \
    --to=simon@superduper.net \
    --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