Message ID | 1581676286-13265-1-git-send-email-srirrama@codeaurora.org (mailing list archive) |
---|---|
Headers | show |
Series | Support hash based reo destination ring selection | expand |
Sriram R <srirrama@codeaurora.org> writes: > Currently, reo destination ring selection is based on pdev, > i.e each pdev is allocated a static reo destintaion ring and > rx packets for the pdev is always received on the ring. > This allows use of only 3 out of 4 reo destination rings at the > max when all pdev's are active and when only one pdev is active > we utilize only one ring and other 3 rings remain idle. > To make effective use of all the reo rings, this patchset enables > hash based reo destination ring selection where the hash is computed > based on the 5-tuple ( src/dst ip, src/dst port, protocol) info > from each packet and is used by hw for destination ring selection. > > Also, current implementation of amsdu list based processing is replaced > with per msdu based handling since the received subframe could be > pushed to different rings after decap based on hash value computed. > > This patchset is based on patchset "ath11k: offload PN verification to the HW" > > Sriram R (2): > ath11k: Configure hash based reo destination ring selection > ath11k: Perform per-msdu rx processing You need to CC linux-wireless, so please resend as v2.