From: Michal Kazior <michal.kazior@tieto.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Noah Causin <n0manletter@gmail.com>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] ath10k fq_codel support
Date: Thu, 13 Oct 2016 17:59:19 +0200 [thread overview]
Message-ID: <CA+BoTQk5WueqPb-0YnL1uxnbqXQN9qTi=wtCR0DO51rTUfgkyw@mail.gmail.com> (raw)
In-Reply-To: <87y41sxnlp.fsf@toke.dk>
On 13 Octsuppber 2016 at 17:41, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Noah Causin <n0manletter@gmail.com> writes:
>
>> Hi,
>>
>> I was looking into getting an Ubiquiti Unifi AC-Pro to flash LEDE onto for
>> testing the ath10k performance and latency with fq_codel.
>>
>> I already have an Archer C7 V2 which uses the ath10k-firmware-qca988x package,
>> which the Unifi AC-Pro and Lite seem to use.
>>
>> Would I have all I need if I flashed the latest git version of LEDE?
>>
>> Also, what firmware versions support the intermediate software queues,
>> and would my Archer C7 be fine for preliminary testing?
>
> You can check if it's active by seeing if you can read
> /sys/kernel/debug/ieee80211/phy0/aqm - if that exists and outputs
> anything when you 'cat' it, the intermediate queues are active.
>
> They are disabled for some hardware revisions, but not sure which ones.
wake_tx_queue is disabled if fw doesn't advertise flow control support
(which is supported in qca99xx and qca40xx chip fw blobs only so far).
qca988x found in archer c7 will have it disabled.
The patch that disables it is [1]. You can revert it or tinker around
the logic it introduced if you want to force fq_codel.
[1]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=4ca1807815aa6801aaced7fdefa9edacc2521767
Michal
next prev parent reply other threads:[~2016-10-13 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 15:27 Noah Causin
2016-10-13 15:41 ` Toke Høiland-Jørgensen
2016-10-13 15:59 ` Michal Kazior [this message]
2016-10-13 16:08 ` Noah Causin
2016-10-13 16:15 ` Toke Høiland-Jørgensen
2016-10-13 23:06 ` Noah Causin
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+BoTQk5WueqPb-0YnL1uxnbqXQN9qTi=wtCR0DO51rTUfgkyw@mail.gmail.com' \
--to=michal.kazior@tieto.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=n0manletter@gmail.com \
--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