Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jon Pike <jonpike54@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake] Current status and recommendations for APU2C*/ArcherC7 and ath10k platforms?
Date: Thu, 20 Apr 2017 15:05:06 -0700	[thread overview]
Message-ID: <CALukJKSgfv_U6cNe3Fn4G+ri4wZ4ME=2ufS3sTpFgVo8L7TjnQ@mail.gmail.com> (raw)
In-Reply-To: <CALukJKQXrU0OmX6iQ5WmxB=TdJJC0=tEWRM1hFmaYr-g6YeGtA@mail.gmail.com>

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

* >1. What's the status of make >wifi fast on the ath10k now, or >did it
*>* make it there yet?
*
>Well, the queue rework is in >there, but only enabled for >certain
>hardware. Not for the Archer, >though...

Bummer...

Is there a handy list of which devices are MWFF functional on ath9k and ath10k?


On Apr 20, 2017 2:13 PM, "Jon Pike" <jonpike54@gmail.com> wrote:

> >The 17.01 LEDE release is great for >both the C7 and the WNDR3800, and
>
> has all the WiFi-related fixes (bufferbloat fixes and airtime fairness)
> included. You'll probably need something beefier for a main gateway at
> those speeds, though. Not sure about the APU2; think it is supported in
> >LEDE as well?
>
> Just a note, I have a C7, and it might just be able to get by at your speeds. Actually, have a 300/30mbit cable connection, so I've done a lot of experimenting to see how much of that it can handle. The limit seems to be about 120-140 (set) with measured speed being 100-125mbit, with Cake running, before my C7 starts hitting 0% idle.  Now, only ingress is that fast, with the egress much slower, not sure if it would he  worse case with both about as fast.  No SQM, or SQM on the 30mbit egress only, and it's good to >340mbit.
>
> Thought this might be a good place to ask a question or two abt the wifi fast stuff... while Toke's listening.
>
> 1. What's the status of make wifi fast on the ath10k now, or did it make it there yet?
>
> 2. Is there any benefit or reason to use (or not) the optional Caldera ath10k driver vs the standard one? (Possibly no MWFF connection)
>
> TNX...
>
>

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

  parent reply	other threads:[~2017-04-20 22:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 21:13 Jon Pike
2017-04-20 21:17 ` Toke Høiland-Jørgensen
2017-04-21  5:13   ` Dave Taht
2017-04-20 22:05 ` Jon Pike [this message]
2017-05-09  2:27   ` Jon Pike

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALukJKSgfv_U6cNe3Fn4G+ri4wZ4ME=2ufS3sTpFgVo8L7TjnQ@mail.gmail.com' \
    --to=jonpike54@gmail.com \
    --cc=cake@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