Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Pete Heist <pete@heistp.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes
Date: Sun, 8 Jul 2018 19:20:56 -0700	[thread overview]
Message-ID: <CALQXh-NEDBSUR8W92WSs8bSbz2EBST0Lp8kavysYg616jAySjQ@mail.gmail.com> (raw)
In-Reply-To: <A520EE5F-332D-41B0-8444-A4A193B70A52@gmail.com>

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

Do the AP-to-AP links use the same packet scheduling as the AP-to-STA
links? (especially the prohibition on aggregation for VO, which seems
counter-productive on a backhaul link).

On Thu, Jul 5, 2018 at 1:17 PM, Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 5 Jul, 2018, at 9:02 pm, Pete Heist <pete@heistp.net> wrote:
> >
> >> Wouldn't be surprised. Note that packets will be dropped from the
> >> longest queue, though, so unresponsive flows just hurt themselves...
> >
> > Probably not before they’ve wasted airtime though and and impacted
> everyone else...
>
> Would it be worth extending the principle of airtime fairness to the QoS
> queues?  Clearly traffic in the VO queue consumes airtime out of all
> proportion to its actual volume, due to the prohibition on aggregation;
> this provokes a similar argument to the impact of slow clients on faster
> ones.
>
> I wouldn't worry too much about the links between leaf APs and their
> clients.  Those are probably relatively strong and fast, so BE traffic can
> get through reasonably well in between the VO traffic.
>
> But the AP-to-AP links cover a significant distance and are that much more
> susceptible to airtime congestion, which VO traffic exacerbates
> considerably.  These APs are also running open-source firmware where we can
> actually tackle this problem.  So there must be a case for deprioritising
> VO if it's using more than some reasonable share of the available airtime.
>
> Oh, and if I find out which BT client has selected a VO-category DSCP by
> default...  >:-(
>
>  - 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: 2484 bytes --]

  reply	other threads:[~2018-07-09  2:20 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-19 16:03 bkil
2018-05-20 18:56 ` Pete Heist
2018-05-31  0:52 ` David Lang
2018-06-08  9:37   ` Pete Heist
2018-06-09 15:32     ` bkil
2018-06-13 13:07       ` Pete Heist
2018-06-13 13:24         ` Toke Høiland-Jørgensen
2018-06-13 16:01           ` Pete Heist
2018-06-30 19:14             ` bkil
2018-07-04 21:47               ` Pete Heist
2018-07-05 13:08                 ` Toke Høiland-Jørgensen
2018-07-05 17:26                   ` Pete Heist
2018-07-05 17:37                     ` Toke Høiland-Jørgensen
2018-07-05 18:02                       ` Pete Heist
2018-07-05 20:17                         ` Jonathan Morton
2018-07-09  2:20                           ` Aaron Wood [this message]
2018-07-09  5:17                             ` Jonathan Morton
2018-07-09  6:27                               ` Pete Heist
2018-07-09 12:55                                 ` Sebastian Moeller
2018-07-09 23:21                                   ` Pete Heist
2018-07-09  5:13                 ` David Lang
2018-07-09 23:33               ` Pete Heist
2018-07-10  0:39                 ` Pete Heist
2018-07-10  7:02                   ` bkil
2018-06-13 16:30           ` Sebastian Moeller
2018-06-13 17:50             ` Toke Høiland-Jørgensen
     [not found]       ` <CADuVhRWL2aVjzjfLHg1nPFa8Ae-hWrGrE7Wga4eUKon3oqoTXA@mail.gmail.com>
2018-06-30 19:26         ` bkil
2018-06-30 20:04           ` Jannie Hanekom
  -- strict thread matches above, loose matches on Subject: below --
2018-04-24  8:33 Pete Heist
2018-04-24 11:54 ` Toke Høiland-Jørgensen
2018-04-24 13:37   ` Pete Heist
2018-04-24 13:51     ` Toke Høiland-Jørgensen
2018-04-24 14:09       ` Pete Heist
2018-04-24 14:34         ` Toke Høiland-Jørgensen
2018-04-24 19:10           ` Pete Heist
2018-04-24 21:32             ` Toke Høiland-Jørgensen
2018-04-25  6:05               ` Pete Heist
2018-04-25  6:36                 ` Sebastian Moeller
2018-04-25 17:17                   ` Pete Heist
2018-04-26  0:41                 ` David Lang
2018-04-26 19:40                   ` Pete Heist
2018-04-26  0:38               ` David Lang
2018-04-26 21:41                 ` Pete Heist
2018-04-26 21:44                   ` Sebastian Moeller
2018-04-26 21:56                     ` Pete Heist
2018-04-26 22:04                       ` David Lang
2018-04-26 22:47                         ` Pete Heist
2018-04-27 10:15                           ` Toke Høiland-Jørgensen
2018-04-27 10:32                             ` Pete Heist
2018-04-26  0:35       ` David Lang
2018-04-27 11:42 ` Valent Turkovic
2018-04-27 11:50   ` Pete Heist
2018-04-27 11:59     ` Valent Turkovic
2018-04-27 12:17       ` Pete Heist
2018-04-27 11:47 ` Valent Turkovic
2018-04-27 12:00   ` Pete Heist

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=CALQXh-NEDBSUR8W92WSs8bSbz2EBST0Lp8kavysYg616jAySjQ@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=chromatix99@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=pete@heistp.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