From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Rich Brown <richb.hanover@gmail.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] New Realtek driver 802.11ax, with FQ-CoDel support!
Date: Thu, 18 Nov 2021 15:52:36 -0800 [thread overview]
Message-ID: <CAA93jw7cqz2M2FX90BOj0_-y57_XdEh1c4N6Grpa3bA5nBJ2eQ@mail.gmail.com> (raw)
In-Reply-To: <87mtnegwfo.fsf@toke.dk>
I am hoping I can finally retire my ath9k and ath10k chips by next
christmas. Apparently amd is leveraging the mediatek MT7921K chip.
https://www.tomshardware.com/news/mediatek-and-amd-team-up-on-wi-fi-6e-chips-for-next-gen-ryzen-pcs
On Tue, Oct 12, 2021 at 7:17 AM Toke Høiland-Jørgensen via
Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net> wrote:
>
> Rich Brown <richb.hanover@gmail.com> writes:
>
> >> On Oct 9, 2021, at 12:00 PM, make-wifi-fast-request@lists.bufferbloat.net wrote:
> >>
> >> In the process of being upstreamed:
> >>
> >> https://lore.kernel.org/r/20211008035627.19463-1-pkshih@realtek.com <https://lore.kernel.org/r/20211008035627.19463-1-pkshih@realtek.com>
> >>
> >>> This driver named rtw89, which is the next generation of rtw88, supports
> >>> Realtek 8852AE 802.11ax 2x2 chip whose new features are OFDMA, DBCC,
> >>> Spatial reuse, TWT and BSS coloring; now some of them aren't implemented
> >>> though.
> >
> > This is so cool! A couple questions:
> >
> > 1) I have lost track: what drivers now incorporate FQ-CoDel?
>
> $ cd drivers/net/wireless && git grep -l wake_tx_queueath/ath10k/mac.c
> ath/ath9k/ath9k.h
> ath/ath9k/main.c
> ath/ath9k/xmit.c
> intel/iwlwifi/mvm/mac80211.c
> mediatek/mt76/mt76.h
> mediatek/mt76/mt7603/main.c
> mediatek/mt76/mt7615/main.c
> mediatek/mt76/mt76x0/pci.c
> mediatek/mt76/mt76x0/usb.c
> mediatek/mt76/mt76x2/pci_main.c
> mediatek/mt76/mt76x2/usb_main.c
> mediatek/mt76/mt7915/main.c
> mediatek/mt76/mt7921/main.c
> mediatek/mt76/tx.c
> realtek/rtw88/mac80211.c
>
> > 2) How can we talk about this in OpenWrt (and elsewhere...)?
> > - Is it correct/reasonable/sensible to say that the fq_codel wifi drivers are "good" while the others are "not-so-good"
> > - Does the presence of a chip/driver from 1) above indicate a more desirable device?
> > - Or is it more nuanced?
>
> For just the FQ-codel in driver support, yeah, I think it's fair to say
> that it's unambiguously "better".
>
> -Toke
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2021-11-18 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1633795201.1059.make-wifi-fast@lists.bufferbloat.net>
2021-10-10 0:09 ` Rich Brown
2021-10-12 14:16 ` Toke Høiland-Jørgensen
2021-11-18 23:52 ` Dave Taht [this message]
2021-10-08 17:46 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
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=CAA93jw7cqz2M2FX90BOj0_-y57_XdEh1c4N6Grpa3bA5nBJ2eQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=richb.hanover@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