mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Hangtian Zhu <hangtian.zhu@oss.qualcomm.com>,
	tglx@kernel.org, jjohnson@kernel.org
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 2/2] wifi: ath12k: enable threaded NAPI when DP IRQ affinity is unavailable
Date: Thu, 18 Jun 2026 15:11:03 +0800	[thread overview]
Message-ID: <19533f4d-9fd7-41ba-bd57-f7af092aaf6a@oss.qualcomm.com> (raw)
In-Reply-To: <20260519011627.713068-3-hangtian.zhu@oss.qualcomm.com>



On 5/19/2026 9:16 AM, Hangtian Zhu wrote:
> Determine threaded NAPI policy from runtime IRQ capability of the DP MSI
> IRQ.
> 
> If irq_can_set_affinity() reports that affinity cannot be set, enable
> threaded NAPI for DP interrupt groups so datapath processing is not
> constrained by a single-CPU softirq context.
> 
> On RB3Gen2, where IRQ affinity is unavailable in the effective IRQ path,
> EHT160 UDP downlink throughput improved from 802 Mbps to 2.58 Gbps after
> enabling threaded NAPI.
> 
> Tested-on: QCC2072 hw1.0 PCI WLAN.COL.1.0.c2-00074-QCACOLSWPL_V1_TO_SILICONZ-1
> 
> Signed-off-by: Hangtian Zhu <hangtian.zhu@oss.qualcomm.com>

Reviewed-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>


  reply	other threads:[~2026-06-18  7:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  1:16 [RESEND PATCH 0/2] genirq/ath12k: fallback to threaded NAPI when " 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 [this message]
2026-06-30 21:26 ` [RESEND PATCH 0/2] genirq/ath12k: fallback to threaded NAPI when " Jeff Johnson

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=19533f4d-9fd7-41ba-bd57-f7af092aaf6a@oss.qualcomm.com \
    --to=baochen.qiang@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®