From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Miguel Catalan Cid <miguel.catalan@i2cat.net>
Cc: make-wifi-fast@lists.bufferbloat.net, linux-wireless@vger.kernel.org
Subject: Re: [Make-wifi-fast] Support for airtime scheduling using ath10k
Date: Tue, 30 Jun 2020 17:41:27 +0200 [thread overview]
Message-ID: <87lfk4ftnc.fsf@toke.dk> (raw)
In-Reply-To: <CAMHmoovWrXhMheEPapgEw9b_7S-jOZdJDRvAp-1Cb_i0=pBfEw@mail.gmail.com>
Miguel Catalan Cid <miguel.catalan@i2cat.net> writes:
> Hi,
>
> Do we need to use a specific firmware? It's ok to use the last one from
> kvalo, or should we use the one from candelatech?
Shouldn't matter, I think; the airtime scheduler tries to do its thing
in software. It does have to work around the firmware, to a certain
extent, though, which I suspect is why it doesn't work quite so well as
on ath9k.
Incidentally, this "impedance mismatch" between scheduler and firmware
is what this patch was supposed to fix:
https://lore.kernel.org/linux-wireless/20191222172423.131033-1-toke@redhat.com/
Never did get around to respinning it, so not sure if it still applies.
If it does, you could try taking it for a spin; otherwise I can try
updating it so you can apply it and test :)
-Toke
next prev parent reply other threads:[~2020-06-30 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMHmoovK_m=Yd4uUPhsdHZ588+d1DF-fyS+uGKdRWvd33Q2u+A@mail.gmail.com>
2020-06-23 9:35 ` [Make-wifi-fast] Support for airtime scheduling using ath10k Toke Høiland-Jørgensen
2020-06-29 9:55 ` Miguel Catalan Cid
2020-06-29 10:25 ` Toke Høiland-Jørgensen
[not found] ` <CAMHmoovWrXhMheEPapgEw9b_7S-jOZdJDRvAp-1Cb_i0=pBfEw@mail.gmail.com>
2020-06-30 15:41 ` Toke Høiland-Jørgensen [this message]
[not found] ` <CAMHmoos8p7icOfsXT7q+-uThGCd-k04hPT0BWiCzNTPqH3CJUQ@mail.gmail.com>
2020-09-11 14:36 ` Toke Høiland-Jørgensen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfk4ftnc.fsf@toke.dk \
--to=toke@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=miguel.catalan@i2cat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.