From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: tglx@kernel.org, jjohnson@kernel.org,
Hangtian Zhu <hangtian.zhu@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 0/2] genirq/ath12k: fallback to threaded NAPI when IRQ affinity is unavailable
Date: Tue, 30 Jun 2026 14:26:16 -0700 [thread overview]
Message-ID: <178285477658.1590147.549685497846838720.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260519011627.713068-1-hangtian.zhu@oss.qualcomm.com>
On Tue, 19 May 2026 09:16:25 +0800, Hangtian Zhu wrote:
> This series improves ath12k datapath behavior on platforms where the
> effective IRQ path for WLAN MSI interrupts does not support affinity
> setting.
>
> In such setups, DP processing cannot be distributed as intended and can
> become CPU-constrained. The ath12k change switches to threaded NAPI when
> runtime IRQ capability indicates affinity is unavailable.
>
> [...]
Applied, thanks!
[1/2] genirq: export irq_can_set_affinity() for module drivers
commit: 25e638447e329f08febae2b64c7f85b3bb95e998
[2/2] wifi: ath12k: enable threaded NAPI when DP IRQ affinity is unavailable
commit: 74e1a4762c79a2d6879495d83f22b83acc4dae33
Best regards,
--
Jeff Johnson <jeff.johnson@oss.qualcomm.com>
prev parent reply other threads:[~2026-06-30 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 1:16 Hangtian Zhu
2026-05-19 1:16 ` [RESEND PATCH 1/2] genirq: export irq_can_set_affinity() for module drivers Hangtian Zhu
2026-05-19 14:30 ` Thomas Gleixner
2026-05-20 2:42 ` Hangtian Zhu
2026-05-20 16:00 ` Jeff Johnson
2026-05-19 1:16 ` [RESEND PATCH 2/2] wifi: ath12k: enable threaded NAPI when DP IRQ affinity is unavailable Hangtian Zhu
2026-06-18 7:11 ` Baochen Qiang
2026-06-30 21:26 ` Jeff Johnson [this message]
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=178285477658.1590147.549685497846838720.b4-ty@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=hangtian.zhu@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tglx@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®