Linux wireless drivers development
 help / color / mirror / Atom feed
From: Leonard Lausen <leonard@lausen.nl>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: leonard@lausen.nl, Luka Gejak <luka.gejak@linux.dev>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-wireless@vger.kernel.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH rtw-next v2 0/2] wifi: rtw88: reduce RTL8822CS SDIO request overhead
Date: Mon, 16 Nov 2026 10:08:01 +0000	[thread overview]
Message-ID: <20261116100804.425592-2-leonard@lausen.nl> (raw)

Reduce RTL8822CS SDIO request overhead by filtering hardware-handled
control frames and combining adjacent TX-capacity reads.

This complete v2 series is based on rtw-next at 61a5eb87b2d9. Changes in v2:
- Rebase both patches onto rtw-next.
- Fix continuation and argument alignment, declaration order, comment
  formatting and long lines throughout the added code.
- Remove the deprecated Assisted-by tag.
- Refresh throughput measurements using the rebased driver.

TCP medians on RTL8822CS/NanoPi M5 with the v2 driver, in Mbit/s:

                              Upload   Download
  rtw-next baseline             165.7      206.7
  Both patches                  296.9      271.2

Together the patches improved median upload by 79.2% and download by 31.2%.
Each configuration used three 20-second TCP samples per direction on a
shared Wi-Fi network, so throughput can vary.

Both driver stacks were built against the running v7.4-rc2 kernel and
hot-loaded. The same test-only adaptation restored the older key-iteration
API and RCU locking in firmware recovery. Both configurations used the
same MMC host stack, 198 MHz SDR104 and performance governors, with SDIO
IRQ on CPU4, iperf client on CPU6 and server on CPU7. Traffic crossed
Wi-Fi/AP/Ethernet between two endpoints on the board.

Independent v1 tests measured a 52% upload and 9% download gain from
filtering alone, and 9% upload and 8% download from combined reads alone.
Adding combined reads after filtering gave another 11% upload and 4%
download. Those tests used v7.4-rc2 with the RX-bounds and MMC voltage-switch
fixes and stock MMC host limits: four 20-second upload samples and four
30-second download samples per configuration on the shared network.

All 20 configured rtw88 module objects compiled and linked as relocatable
objects on ARM64 with W=1 after each patch, without warnings. Runtime
builds passed modpost; loaded module IDs, traffic paths and register
settings were checked. MMC traces confirmed three 4-byte capacity reads
became one 12-byte read, with zero SDIO command errors.
No full rtw-next kernel was booted or installed module files replaced.
AP/monitor, suspend/resume and other-chip hardware remain untested.

AI assistance: Codex helped develop the code, inspect vendor sources,
automate the earlier benchmarks, rebase the series, apply style fixes
and draft the messages.

v1: https://lore.kernel.org/linux-wireless/20261115142330.359247-2-leonard@lausen.nl/

Leonard Lausen (2):
  wifi: rtw88: 8822c: filter hardware-handled control frames on SDIO
  wifi: rtw88: sdio: combine free TX page register reads

 drivers/net/wireless/realtek/rtw88/reg.h      |  4 ++
 drivers/net/wireless/realtek/rtw88/rtw8822c.c | 10 +++
 drivers/net/wireless/realtek/rtw88/sdio.c     | 63 +++++++++++++++++--
 drivers/net/wireless/realtek/rtw88/sdio.h     |  1 +
 4 files changed, 74 insertions(+), 4 deletions(-)


base-commit: 61a5eb87b2d9b4d5e353780b781cf691f39ba9e1

             reply	other threads:[~2026-11-16 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 10:08 Leonard Lausen [this message]
2026-11-16 10:08 ` [PATCH rtw-next v2 1/2] wifi: rtw88: 8822c: filter hardware-handled control frames on SDIO Leonard Lausen
2026-11-16 16:30   ` Luka Gejak
2026-11-16 10:08 ` [PATCH rtw-next v2 2/2] wifi: rtw88: sdio: combine free TX page register reads Leonard Lausen

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=20261116100804.425592-2-leonard@lausen.nl \
    --to=leonard@lausen.nl \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    --cc=pkshih@realtek.com \
    --cc=shawn.lin@rock-chips.com \
    /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