Manikanta Pubbisetty <quic_mpubbise@xxxxxxxxxxx> writes: > Currently in the case of WCN6750, only one TCL ring is used for TX, > this is limiting the TX throughput in 160 MHz case, enabling multiple > TCL rings on WCN6750 has shown an improvement of nearly 300 Mbps in > the case of TCP TX, therefore add the support of multi TX ring for > WCN6750. > > Currently TCL ring is selected based on CPU ID, this logic cannot be > applied for WCN6750 as there is chance of out of order TX of packets > and to avoid this, choose TCL ring based on flow hash so that packets > of the same flow will end up on same TCL ring. For the same reason, > TCL ring retry logic is also not applicable for WCN6750. > > Also the mapping of TCL, WBM & RBM IDs for WCN6750 is different from > existing devices. Create a new TCM/WBM/RBM mapping for WCN6750. > > Change does not impact existing ath11k devices. It would also nice to document _why_ it doesn't impact existing (or do you mean "other"?) devices. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
