Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Cc: Felix Fietkau <nbd@nbd.name>
Subject: [Make-wifi-fast] what's in lede-head for fq_codel?
Date: Sun, 4 Sep 2016 19:13:46 -0700	[thread overview]
Message-ID: <CAA93jw6yvcXWCrBr6oV_T_zr_k7qf7+azdHrXJaqb4NE6CxXJw@mail.gmail.com> (raw)

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

I started evaluating the ubnt ac lite as a new platform to use for
testing - they have good antennas and do gigE POE (which makes it
easier to lay out a distance test) - installing lede was a snap and I
got 450+mbits throughput out of them on vht80. Looking *nice*...

... But my mission was to look at latencies at lower rates, so I tried
out mcs1,4,minstrel at ht20 on the ath9k component of this AP.

Looks like progress.

My *guess* from looking at this plot (40ms median latency), (misnamed,
just look at bandwidth groupings) - was

* ath9k

ath9 intermediate queues are enabled
codel is still set to target 20ms rather than 5ms
fq is still disabled (and quantum 300, rather than 1514)
no toke airtime fairness

* ath10k

intermediate queues disabled, no fq_codel at all

Please note, I'm not complaining, just confirming... I needed a
baseline!! I've been mostly leveraging toke's builds, from felix's
staging tree, which are much closer to the whole enchalada...

But what's next for staging or head? Are all the relevant ath10k bits in there?

-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

[-- Attachment #2: flatishlatency.png --]
[-- Type: image/png, Size: 226651 bytes --]

                 reply	other threads:[~2016-09-05  2:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw6yvcXWCrBr6oV_T_zr_k7qf7+azdHrXJaqb4NE6CxXJw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=nbd@nbd.name \
    /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