From: Ho Jie Feng <hjf3108@gmail.com>
To: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: linux-wireless@vger.kernel.org, Ho Jie Feng <hjf3108@gmail.com>
Subject: [PATCH wireless-next 0/8] wifi: rt2x00: improve the throughput of rt2800usb
Date: Thu, 29 Oct 2026 21:47:41 +0800 [thread overview]
Message-ID: <20261029134752.1299130-1-hjf3108@gmail.com> (raw)
This series improves the throughput of rt2800usb.
Implements
- Frequency offset calibration
- Better fallback rates
- Aggregation
- GRO
Tested on WNDA4100 RT3593, 5 GHz with perf3
patch before after
TX RX TX RX
2 crystal calibration 27.7 31.6 28.5 69.7
4 MCS16 to MCS8 TX status 27.0 70.0 29.4 70.0
7 RX bulk aggregation 30.5 67.8 30.5 80.9
8 threaded NAPI with GRO 30.5 80.9 30.5 161.7
RT3070 did not have any visible change for both TX and RX.
Ho Jie Feng (8):
wifi: rt2x00: start the link tuner when an interface is added
wifi: rt2800: calibrate the crystal of RT3593 with the beacons
wifi: rt2800: use the 3SS fallback table of RT3883 on RT3593
wifi: rt2800: report the MCS16 to MCS8 fallback of RT3593 in TX status
wifi: rt2800: don't report an A-MPDU length to minstrel_ht
wifi: rt2800: set the mac80211 fast-xmit and aggregation flags
wifi: rt2800usb: enable RX bulk aggregation
wifi: rt2x00usb: use a threaded NAPI with GRO for RX
drivers/net/wireless/ralink/rt2x00/rt2800.h | 1 +
.../net/wireless/ralink/rt2x00/rt2800lib.c | 115 +++++++++++++++++-
.../net/wireless/ralink/rt2x00/rt2800lib.h | 4 +
.../net/wireless/ralink/rt2x00/rt2800usb.c | 33 ++++-
.../net/wireless/ralink/rt2x00/rt2800usb.h | 6 +
drivers/net/wireless/ralink/rt2x00/rt2x00.h | 16 ++-
.../net/wireless/ralink/rt2x00/rt2x00dev.c | 105 ++++++++++++----
.../net/wireless/ralink/rt2x00/rt2x00lib.h | 2 +
.../net/wireless/ralink/rt2x00/rt2x00link.c | 9 ++
.../net/wireless/ralink/rt2x00/rt2x00mac.c | 6 +
.../net/wireless/ralink/rt2x00/rt2x00mmio.c | 2 +-
.../net/wireless/ralink/rt2x00/rt2x00usb.c | 52 ++++++--
12 files changed, 307 insertions(+), 44 deletions(-)
base-commit: 734bef548a96e8774d6eef5dfa2026c6edc4e80b
--
2.53.0
next reply other threads:[~2026-10-29 13:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 13:47 Ho Jie Feng [this message]
2026-10-29 13:47 ` [PATCH wireless-next 1/8] wifi: rt2x00: start the link tuner when an interface is added Ho Jie Feng
2026-10-29 13:47 ` [PATCH wireless-next 2/8] wifi: rt2800: calibrate the crystal of RT3593 with the beacons Ho Jie Feng
2026-10-29 13:47 ` [PATCH wireless-next 3/8] wifi: rt2800: use the 3SS fallback table of RT3883 on RT3593 Ho Jie Feng
2026-10-29 13:47 ` [PATCH wireless-next 4/8] wifi: rt2800: report the MCS16 to MCS8 fallback of RT3593 in TX status Ho Jie Feng
2026-10-29 13:47 ` [PATCH wireless-next 5/8] wifi: rt2800: don't report an A-MPDU length to minstrel_ht Ho Jie Feng
2026-10-29 13:47 ` [PATCH wireless-next 6/8] wifi: rt2800: set the mac80211 fast-xmit and aggregation flags Ho Jie Feng
2026-10-30 9:17 ` Stanislaw Gruszka
2026-10-30 11:33 ` Jie Feng
2026-10-29 13:47 ` [PATCH wireless-next 7/8] wifi: rt2800usb: enable RX bulk aggregation Ho Jie Feng
2026-10-29 13:47 ` [PATCH wireless-next 8/8] wifi: rt2x00usb: use a threaded NAPI with GRO for RX Ho Jie Feng
2026-10-30 9:10 ` [PATCH wireless-next 0/8] wifi: rt2x00: improve the throughput of rt2800usb Stanislaw Gruszka
2026-10-30 11:30 ` Jie Feng
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=20261029134752.1299130-1-hjf3108@gmail.com \
--to=hjf3108@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
/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