Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] openwrt freeze jan 1
Date: Fri, 18 Dec 2020 15:25:50 -0800	[thread overview]
Message-ID: <CALQXh-Ospweh9NONX6qx20OS6hHq2mTPRR+G85qUVDW2JZaKAw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw56aOMUFDyap_gWNFZ5NqEOKCte9mKfkB3NpQY4JbUBqA@mail.gmail.com>

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

Wait, the AQL changes for ath10k aren't in 19.07?  I'm seeing the
aqm/airtime fairness controls/stats, but don't know what to look for in
/sys/kernel to see if AQL is present (if it's visible there at all), or if
I'm going to have to run side-by-side tests...

Relatedly, the current 80211 queue setup is still using the 4 traffic-class
queues per station, correct?  Is there any way to turn that off without
building your own kernel?

(I recently upgraded my "main" AP to an Archer A7 v5 (ath10k), and moved
the WRT1900AC out to a place where it will see fewer simultaneous clients
(and inserted a dedicated router for WAN, but that's a separate thread).

On Tue, Dec 15, 2020 at 9:49 AM Dave Taht <dave.taht@gmail.com> wrote:

> If you have any spare time this upcoming holiday to play with openwrt
> head....
>
> I note that this is apparently not in there as yet:
> https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002
>
> (and after much testing I settled on a 10ms target and found that
> retries were really the next
> big problem messing things up. Felix also found and fixed a few other
> bugs related to aql). I am
> hoping to clear some time myself to see where things stand.
>
>
>
> --
> "For a successful technology, reality must take precedence over public
> relations, for Mother Nature cannot be fooled" - Richard Feynman
>
> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 2416 bytes --]

  reply	other threads:[~2020-12-18 23:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 17:49 Dave Taht
2020-12-18 23:25 ` Aaron Wood [this message]
2020-12-19 12:46   ` Toke Høiland-Jørgensen
2020-12-20  3:29 ` Valdis Klētnieks

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/cerowrt-devel.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-Ospweh9NONX6qx20OS6hHq2mTPRR+G85qUVDW2JZaKAw@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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