Re: [PATCH ath-next] wifi: ath12k: Use different RX release ring sizes as per memory profiles

On 7/21/2026 7:04 PM, Pavankumar Nandeshwar wrote:
> Currently, the RX release ring size is hardcoded to 1024 entries via
> DP_RX_RELEASE_RING_SIZE. This value was sufficient for older generations,
> but is not adequate for Wi-Fi 7 scenarios with higher aggregation,
> parallel processing, and increased likelihood of error bursts.
> 
> In Wi-Fi 7, a PPDU can carry up to 1024 MPDUs and each MPDU may contain
> multiple MSDUs. In error scenarios such as REO out-of-order (OOR) events,
> a large number of MSDUs can be pushed to the RX release ring in a short
> duration. With multiple PPDUs being processed in parallel (e.g. multi-core
> or MLO scenarios), this can lead to significant bursts of descriptors.
> 
> Field observations have shown frequent OOR conditions and back-pressure
> issues with smaller ring sizes. Increasing the RX release ring size helps
> absorb these bursts and avoids back-pressure in the RXDMA/REO pipeline.
> Without sufficient ring capacity (e.g. 16K), back-pressure was observed
> under stress conditions.
> 
> To address this, make the RX release ring size configurable per memory
> profile by adding rx_release_ring_size to ath12k_dp_profile_params:
> 
> - Default memory profile: 16384 entries
> - Low memory profile (512M): 8192 entries
> 
> The larger size in the default profile improves robustness under high
> traffic and error conditions by reducing the probability of ring overflow
> and pipeline stalls. The reduced size in the low memory profile balances
> memory usage while still providing sufficient headroom compared to the
> previous fixed value.
> 
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
> 
> Signed-off-by: Pavankumar Nandeshwar <[email protected]>

Reviewed-by: Baochen Qiang <[email protected]>