From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: Yingying Tang <yingying.tang@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, yintang@qti.qualcomm.com
Subject: Re: [PATCH ath-next] wifi: ath12k: change MAC buffer ring size to 4096
Date: Fri, 23 Oct 2026 11:13:56 +0800 [thread overview]
Message-ID: <38fc5a6d-c019-43bb-98f6-ba6a667c64e1@oss.qualcomm.com> (raw)
In-Reply-To: <atrJv0wgF20tmuDr@QCOM-aGQu4IUr3Y>
On 10/23/2026 10:43 AM, Shawn Guo wrote:
> On Fri, Oct 23, 2026 at 10:13:18AM +0800, Baochen Qiang wrote:
>> On 10/22/2026 9:44 PM, Shawn Guo wrote:
>
> [...]
>
>>> I bisected drivers/net/wireless/ath/ath12k between v7.3 (broken) and
>>> the ath tag (working). It lands on:
>>>
>>> 15f7603b69a8 ("wifi: ath12k: Increase RXDMA buffer ring size for default memory profile")
>>>
>>> The previous commit, 643f0bf93617, still has 4096 entries and is broken.
>>> 15f7603b69a8 changes one line, .rxdma_buf_ring_size from 4096 to 8192,
>>> and works.
>>
>> thanks for sharing this. I can repro it using the 481 firmware once get 15f7603b69a8 reverted.
>
> Thanks for confirming!
>
>> so the rule here seems that rxdma_buf_ring_size must be at least twice as large as
>> DP_RX_MAC_BUF_RING_SIZE (I also tries four times large, it works). This rule looks
>> reasonable to me, since WCN7850 get twos HW MACs and its firmware setups rx_mac_buf ring
>> for each, and each ring fills itself using the buffers all from the single RXDMA buffer ring.
>>
>> maybe I should submit a patch mandate this rule.
>
> I'm more concerned about how we would fix the regression for 7.3.x stable
> kernel.
we can try to ask stable team to backport 15f7603b69a8 ?
next prev parent reply other threads:[~2026-10-23 3:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 3:13 [PATCH ath-next] wifi: ath12k: change MAC buffer ring size to 4096 Yingying Tang
2026-06-29 2:16 ` Baochen Qiang
2026-06-29 5:40 ` Rameshkumar Sundaram
2026-06-30 21:26 ` Jeff Johnson
2026-10-20 8:53 ` Shawn Guo
2026-10-21 5:08 ` Manivannan Sadhasivam
2026-10-22 2:30 ` Baochen Qiang
2026-10-22 9:20 ` Shawn Guo
2026-10-22 11:00 ` Baochen Qiang
2026-10-22 13:38 ` Shawn Guo
2026-10-23 1:59 ` Baochen Qiang
2026-10-22 13:44 ` Shawn Guo
2026-10-23 2:13 ` Baochen Qiang
2026-10-23 2:43 ` Shawn Guo
2026-10-23 3:13 ` Baochen Qiang [this message]
2026-10-23 3:44 ` Shawn Guo
2026-10-23 4:42 ` Baochen Qiang
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=38fc5a6d-c019-43bb-98f6-ba6a667c64e1@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=shengchao.guo@oss.qualcomm.com \
--cc=yingying.tang@oss.qualcomm.com \
--cc=yintang@qti.qualcomm.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