From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: jjohnson@kernel.org
Cc: ath11k@lists.infradead.org, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Subject: [PATCH v2 0/3] ath11k/ath12k: implement TX flow control
Date: Wed, 15 Jul 2026 14:50:13 +0200 [thread overview]
Message-ID: <20260715125017.277242-1-jtornosm@redhat.com> (raw)
This series implements custom wake_tx_queue operations for ath11k and
ath12k drivers to prevent hardware ring overflow issues under heavy
traffic.
Without proper flow control, both drivers experience -ENOMEM errors
("failed to transmit frame -12") when the hardware TCL ring fills up.
Additionally, ath12k can hang under sustained high throughput. These
issues are more commonly observed in VMs with PCIe passthrough but
also occur on bare metal systems.
The implementation follows the pattern used in the iwlwifi driver,
checking hardware ring space before dequeuing packets from mac80211.
Per-ring locking serializes ring access while allowing TX completions
to run, preventing deadlocks.
Testing shows stable operation with eliminated -ENOMEM errors, no hangs,
and improved throughput under heavy traffic conditions.
Jose Ignacio Tornos Martinez (3):
mac80211: add ieee80211_tx_peek API
wifi: ath11k: implement custom wake_tx_queue with flow control
wifi: ath12k: implement custom wake_tx_queue with flow control
v2: Address feedback from Zhi-Jun You:
- Add ieee80211_tx_peek() API in mac80211 to peek at the next frame
without dequeuing, enabling accurate ring selection before dequeue
- Use get_ring_selector() on the peeked skb to determine the exact
target ring matching dp_tx, fixing ring mismatch on multi-ring
platforms (ipq8074, wcn6750, qcn9274, wcn7850)
Address feedback from Tamizh Chelvam Raja:
- Fix ath12k radio assignment: obtain ar from txq->vif through the
arvif chain instead of ah->radio flexible array
Move CRASH_FLUSH check inside the TX loop
v1: https://lore.kernel.org/all/20260710155443.1761760-1-jtornosm@redhat.com/
--
2.49.0
next reply other threads:[~2026-07-15 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 12:50 Jose Ignacio Tornos Martinez [this message]
2026-07-15 12:50 ` [PATCH v2 1/3] mac80211: add ieee80211_tx_peek API Jose Ignacio Tornos Martinez
2026-07-15 12:50 ` [PATCH v2 2/3] wifi: ath11k: implement custom wake_tx_queue with flow control Jose Ignacio Tornos Martinez
2026-07-16 1:49 ` Tamizh Raja
2026-07-17 6:17 ` Jose Ignacio Tornos Martinez
2026-07-15 12:50 ` [PATCH v2 3/3] wifi: ath12k: " Jose Ignacio Tornos Martinez
2026-07-16 1:57 ` Tamizh Raja
2026-07-17 6:18 ` Jose Ignacio Tornos Martinez
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=20260715125017.277242-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
all inboxes | Powered by JetHome®