From: Michal Kazior <michal.kazior@tieto.com>
To: David Lang <david@lang.hm>
Cc: Luca Muscariello <luca.muscariello@gmail.com>,
"make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Thoughts on tackling airtime fairness
Date: Thu, 12 May 2016 10:48:29 +0200 [thread overview]
Message-ID: <CA+BoTQnwL3XvCtoNhOQ1R_Eyoj-3jJ8=+SNToepRfuJpy_mA9Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1605120135320.2408@nftneq.ynat.uz>
On 12 May 2016 at 10:40, David Lang <david@lang.hm> wrote:
> I actually have hopes that it will help in the (fairly common) case of
> multiple stations streaming video from the Internet at the same time. If the
> AP -> endpoint traffic can send to multiple stations in the same txop, it
> can greatly reduce the amount of airtime needed.
>
> unfortunantly, from what I hear, the factory AP firmware breaks down if
> there are more than about a dozen stations connected, just as it becomes the
> most valuable.
FWIW There are some firmware changes in some recent ath10k for qca99x0
hardware which involves firmware performing more sophisticated
scheduling coordinated with the host driver (not sure how much of it
is available publicly, yet). The host driver exposes queue depth of
each station/tid and firmware asks host to submit frames to given
station/tid within advertised byte/packet limits.
This is supposed to be "fast" even with up to 50 MU-MIMO clients. I
didn't really get to test it fully from a latency point of view with
flent yet (and I only have 10 MU clients at my disposal currently).
Michał
next prev parent reply other threads:[~2016-05-12 8:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 12:19 Toke Høiland-Jørgensen
2016-05-11 12:55 ` Luca Muscariello
2016-05-11 13:45 ` Toke Høiland-Jørgensen
2016-05-11 14:48 ` Luca Muscariello
2016-05-11 15:10 ` Toke Høiland-Jørgensen
2016-05-11 15:17 ` David Lang
2016-05-11 15:20 ` David Lang
2016-05-11 15:28 ` Toke Høiland-Jørgensen
2016-05-11 15:33 ` Luca Muscariello
2016-05-11 16:19 ` Dave Taht
2016-05-11 16:29 ` Dave Taht
2016-05-11 16:40 ` Toke Høiland-Jørgensen
2016-05-11 16:33 ` Luca Muscariello
2016-05-11 15:07 ` David Lang
2016-05-12 15:59 ` Dave Taht
2016-05-11 15:04 ` David Lang
2016-05-11 16:09 ` Luca Muscariello
2016-05-11 16:41 ` Dave Taht
2016-05-11 18:13 ` Dave Taht
2016-05-12 7:26 ` Michal Kazior
2016-05-12 8:21 ` Luca Muscariello
2016-05-12 8:40 ` David Lang
2016-05-12 8:48 ` Michal Kazior [this message]
2016-05-11 18:28 ` Luca Muscariello
2016-05-11 18:35 ` Luca Muscariello
2016-05-11 15:03 ` David Lang
2016-05-11 15:15 ` Toke Høiland-Jørgensen
2016-05-11 15:24 ` David Lang
2016-05-11 16:35 ` moeller0
2016-05-11 23:25 ` David Lang
2016-05-12 6:41 ` moeller0
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='CA+BoTQnwL3XvCtoNhOQ1R_Eyoj-3jJ8=+SNToepRfuJpy_mA9Q@mail.gmail.com' \
--to=michal.kazior@tieto.com \
--cc=david@lang.hm \
--cc=luca.muscariello@gmail.com \
--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