Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Noah Causin <n0manletter@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] ath10k latency under load?
Date: Fri, 9 Feb 2018 10:56:38 -0500	[thread overview]
Message-ID: <58c8a193-8452-6cd2-3e57-c28309afd858@gmail.com> (raw)
In-Reply-To: <87o9qgutx3.fsf@toke.dk>

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

Last year, mac80211 softqueues were re-enabled for ath10k devices in 
LEDE, which brought back fq_codel support, but did not improve latency 
under load.

Is this latency under load still an issue today?

Noah

On 9/12/2017 5:51 AM, Toke Høiland-Jørgensen wrote:
> Toke Høiland-Jørgensen <toke@toke.dk> writes:
>
>> Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
>>
>>> On 11/09/17 19:33, Adrian Popescu wrote:
>>>> I've tried a bunch of setups: standard firmware, CT firmware, CT
>>>> firmware with the patch and standard firmware with the patch.
>>>>
>>>> Both CT and default firmware have low throughput with this patch.
>>> It's been committed in LEDE
>>> https://git.lede-project.org/?p=source.git;a=commit;h=76c3a033f63aba10047a141ccdae303bc9db571e
>> Ah! So it should be in current nightlies. I'll flash an Archer C7 and
>> see if there are any issues. Anyone else care to test out the current
>> nightly? :)
> So testing it, I see no difference in throughput on my Archer C7; my
> 802.11ac-capable phone gets ~200 Mbps and my 802.11n laptop around 80.
> However, there's no improvement in latency under load either. Meh...
>
> Plot attached.
>
> -Toke
>
>
>
> _______________________________________________
> 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: 2603 bytes --]

  parent reply	other threads:[~2018-02-09 15:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1504713601.28249.make-wifi-fast@lists.bufferbloat.net>
2017-09-11  3:11 ` [Make-wifi-fast] Make-wifi-fast Digest, Vol 29, Issue 1 Jon Pike
2017-09-11  7:33   ` Toke Høiland-Jørgensen
2017-09-11 12:09     ` Adrian Popescu
2017-09-11 12:24       ` Toke Høiland-Jørgensen
2017-09-11 12:30         ` Adrian Popescu
2017-09-11 12:34           ` Toke Høiland-Jørgensen
2017-09-11 17:08             ` Dave Taht
2017-09-11 17:09               ` Dave Taht
2017-09-11 18:33                 ` Adrian Popescu
2017-09-12  9:14                   ` Kevin Darbyshire-Bryant
2017-09-12  9:20                     ` Toke Høiland-Jørgensen
2017-09-12  9:51                       ` Toke Høiland-Jørgensen
2017-09-12 14:03                         ` Adrian Popescu
2017-09-12 17:03                           ` Toke Høiland-Jørgensen
2018-02-09 15:56                         ` Noah Causin [this message]
2018-02-11 12:54                           ` [Make-wifi-fast] ath10k latency under load? Toke Høiland-Jørgensen
2018-02-11 19:32                             ` Jim Gettys
2017-09-11  8:17   ` [Make-wifi-fast] Make-wifi-fast Digest, Vol 29, Issue 1 Kevin Darbyshire-Bryant

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=58c8a193-8452-6cd2-3e57-c28309afd858@gmail.com \
    --to=n0manletter@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