RE: [PATCH v1] net/iavf: fix select wrong scan hw ring by rxdid

.org > Subject: RE: [PATCH v1] net/iavf: fix select wrong scan hw ring by rxdid > > > > > -Original Message- > > From: Xing, Beilei > > Sent: Wednesday, March 16, 2022 4:12 PM > > To: Yang, SteveX ; dev@dpdk.org > > Cc: Wu, Jingjing ; Zhang, Qi Z >

RE: [PATCH v1] net/iavf: fix select wrong scan hw ring by rxdid

> -Original Message- > From: Xing, Beilei > Sent: Wednesday, March 16, 2022 4:12 PM > To: Yang, SteveX ; dev@dpdk.org > Cc: Wu, Jingjing ; Zhang, Qi Z > ; sta...@dpdk.org > Subject: RE: [PATCH v1] net/iavf: fix select wrong scan hw ring by rxdid > > &

RE: [PATCH v1] net/iavf: fix select wrong scan hw ring by rxdid

> -Original Message- > From: Yang, SteveX > Sent: Monday, March 14, 2022 5:32 PM > To: dev@dpdk.org > Cc: Wu, Jingjing ; Xing, Beilei > ; > Zhang, Qi Z ; Yang, SteveX ; > sta...@dpdk.org > Subject: [PATCH v1] net/iavf: fix select wrong scan hw ring by rxd

[PATCH v1] net/iavf: fix select wrong scan hw ring by rxdid

When setup RX queue, the rxdid would be changed if it's "IAVF_RXDID_LEGACY_0/1", that caused the scan hw ring used the wrong function 'iavf_rx_scan_hw_ring_flex_rxd()'. Ignore the rxdid changed when equals "IAVF_RXDID_LEGACY_0/1". Fixes: 0ed16e01313e ("net/iavf: fix function pointer in multi-proc