Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Luca Muscariello <luca.muscariello@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "make-wifi-fast@lists.bufferbloat.net"
	<make-wifi-fast@lists.bufferbloat.net>
Subject: [Make-wifi-fast] On the 802.11 performance anomaly and an airtime fairness scheduler to fix it
Date: Sun, 3 Jul 2016 08:55:25 +0200	[thread overview]
Message-ID: <CAHx=1M4UyVU6PwVB8wF2p94dDpgPZdo1Ci_jwhRM5CEOBR6ydg@mail.gmail.com> (raw)
In-Reply-To: <87ziq2o07z.fsf@toke.dk>

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

Toke,

great piece of work.
UDP tests show that the scheduler is working quite well.
TCP tests: no news that ACK streams are a problem.
This is another well known issue  in wifi.

Every data packet is ACKed already at L2 and L4
sends an ACK that is non contention free.

There is an NSDI paper in 2014 that proposes to use the L2 ACK to carry the
L4 ACK.
It works well but purists might hate that approach.

BTW the gains you show are huge.
If you add multiple stations uniformly distributed around the AP you'll see
tremendous gains.

The delay gain is also huge and poorly explored so far.

On Thu, Jun 30, 2016 at 11:06 PM, Toke Høiland-Jørgensen <toke@toke.dk
<javascript:_e(%7B%7D,'cvml','toke@toke.dk');>> wrote:

> I've previously posted my airtime fairness scheduler patch here. When I
> did I promised a more thorough performance evaluation of it. This took a
> bit longer to get done than I had anticipated, but I have now put up a
> blog post with some pretty graphs.
>
> The post also explains the background of the 802.11 performance anomaly
> to those not familiar with it; feel free to skip to the results if you
> are already familiar with it.
>
> Link:
> https://blog.tohojo.dk/2016/06/fixing-the-wifi-performance-anomaly-on-ath9k.html
>
> -Toke
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> <javascript:_e(%7B%7D,'cvml','Make-wifi-fast@lists.bufferbloat.net');>
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>

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

  parent reply	other threads:[~2016-07-03  6:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 21:06 Toke Høiland-Jørgensen
2016-07-01 13:31 ` Sebastian Moeller
2016-07-01 23:10 ` Dave Taht
2016-07-02 10:26 ` Dave Taht
2016-07-03  6:55 ` Luca Muscariello [this message]
2016-07-03  7:06   ` David Lang
2016-07-03  7:50     ` Jonathan Morton
2016-07-03  7:53       ` Luca Muscariello
2016-07-03  8:03       ` David Lang
2016-07-03  9:07         ` Jonathan Morton

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='CAHx=1M4UyVU6PwVB8wF2p94dDpgPZdo1Ci_jwhRM5CEOBR6ydg@mail.gmail.com' \
    --to=luca.muscariello@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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