Sriram R <srirrama@xxxxxxxxxxxxxx> wrote:
> As Hash based reo destination selection is configured,
> the decapped packets reach different reo destintion rings
> based on the destintaion ring selected for the computed hash (based on
> the 5-tuple {ip src/ip dst/src port/dst port/protocol}) by hw and
> as configured by driver.
>
> Hence the current implementation of amsdu list based processing after all
> the subframes of amsdu are received (since all msdu's for a pdev are
> received in same reo dest ring), is not applicable here and hence is
> replaced with per msdu based handling as these subframes
> can be received in different reo dest rings.
>
> Also, as some of the rx descriptor fields might be valid only for the
> first msdu (for ex. received 80211 header, encryption type, etc),
> it might not be useful now as we cannot sync between different
> subframes received in different rings. Hence do not rely on those
> fields and replace them with fieds valid only on per msdu descriptors.
> Also cache other details such as encryption type for a peer so that
> it can be reused when a packet is received from it.
>
> Co-developed-by: Tamizh Chelvam Raja <tamizhr@xxxxxxxxxxxxxx>
> Signed-off-by: Tamizh Chelvam Raja <tamizhr@xxxxxxxxxxxxxx>
> Signed-off-by: Sriram R <srirrama@xxxxxxxxxxxxxx>
> Signed-off-by: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
New warnings:
drivers/net/wireless/ath/ath11k/dp_rx.c:2010: multiple assignments should be avoided
drivers/net/wireless/ath/ath11k/dp_rx.c:2160: Please don't use multiple blank lines
Fixed in the pending branch.
--
https://patchwork.kernel.org/patch/11385033/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
