Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Trevor Paskett <snoopytjp@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: make-wifi-fast@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] AREDN and Make Wifi Fast
Date: Sat, 06 Feb 2016 19:50:46 -0000	[thread overview]
Message-ID: <66535894-9843-40F6-B78E-3D6E2D22613A@gmail.com> (raw)
In-Reply-To: <56B635A1.8080603@taht.net>

Thanks for the info, we will test these changes in our lab.

With wifi are you using fq_codel alone or with htb? If with htb how are you determining the rates to use?

If you could share the tc / iptables commands you are using in the yurtlab that would help alot.

> On Feb 6, 2016, at 11:04 AM, Dave Täht <dave@taht.net> wrote:
> 
> The simplest thing you can do today to improve latency on your ath9k
> devices is to disable wmm (802.11e), and to reduce the ath9k driver
> queues to smaller sizes. I typically run the yurtlab network with a
> qlen_be of 12 (slow links) to 24 rather than the default.
> 
> On links with significant speed issues, congestion or interference, I
> typically increase the fq_codel target to 20ms.
> 
> We have fiddled with using large quantums with per-dst FQ on ptp links
> with some success on top of that.
> 
> In all cases it helps to have a set of flent runs for each change.
> Throughput will drop, fairness and latency will improve. The yurtlab
> userbase is generally oblivious to a speed problem, it's having low
> latency for gaming, dns, and basic web traffic that works for them.
> 
> None of the above are "optimal" fixes in any way, but perhaps you will
> get some use from them.


  reply	other threads:[~2016-02-06 19:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C421D4AF-51DB-4A6B-A240-B6206C71EC9C@gmail.com>
     [not found] ` <CAA93jw5iRyLcDVm6inXUeWkh9seC4fUrEtOfoea1NiSUtsoJJg@mail.gmail.com>
     [not found]   ` <56AA90C9.6050504@taht.net>
     [not found]     ` <C4BFDD36-D50C-4189-AE30-BCA1E4FF2219@gmail.com>
     [not found]       ` <56B0FE22.3050704@taht.net>
     [not found]         ` <73AA134D-76DC-4D37-94F0-CC3C4FEAF5C6@gmail.com>
     [not found]           ` <56B12DE1.8040009@taht.net>
     [not found]             ` <79F77DD2-2BFF-4697-A118-25D17FD06CBB@gmail.com>
     [not found]               ` <56B15105.7040405@taht.net>
     [not found]                 ` <0BAB0F1C-9F93-4579-9426-648CBE1EF5D5@gmail.com>
2016-02-06 17:44                   ` Dave Täht
2016-02-06 18:04                     ` Dave Täht
2016-02-06 19:50                       ` Trevor Paskett [this message]
2016-02-07 19:18                     ` [Make-wifi-fast] [Cerowrt-devel] " Stephen Hemminger
2016-02-07 19:36                       ` Dave Taht
2016-03-17 11:00                       ` Toke Høiland-Jørgensen
2016-02-27  0:25                     ` [Make-wifi-fast] " David Lang

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=66535894-9843-40F6-B78E-3D6E2D22613A@gmail.com \
    --to=snoopytjp@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave@taht.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