[PATCH 1/3] net/iavf: fix Tx vector path selection logic again

[Ciara Loftus]

Commit b39aeea703b8 ("net/iavf: fix Tx vector path selection logic")
fixed an issue which caused the scalar path to be chosen even when the
AVX-512 path could have been a viable candidate. The commit
be1a887b83cd ("net/iavf: use the new common vector capability function")
accidentally undid this fix, so this commit fixes this again, this time
in a new way due to the changed code landscape since the last fix.

Fixes: be1a887b83cd ("net/iavf: use the new common vector capability function")

Signed-off-by: Ciara Loftus <ciara.loftus at intel.com>
---
 drivers/net/intel/iavf/iavf_rxtx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/intel/iavf/iavf_rxtx.c b/drivers/net/intel/iavf/iavf_rxtx.c
index ab44558a85..ce0a12c348 100644
--- a/drivers/net/intel/iavf/iavf_rxtx.c
+++ b/drivers/net/intel/iavf/iavf_rxtx.c
@@ -4090,7 +4090,7 @@ iavf_set_tx_function(struct rte_eth_dev *dev)
 				    dev->data->port_id);
 			tx_func_type = IAVF_TX_SSE;
 		}
-		if (use_avx2) {
+		if (!use_avx512 && use_avx2) {
 			if (check_ret == IAVF_VECTOR_PATH) {
 				tx_func_type = IAVF_TX_AVX2;
 				PMD_DRV_LOG(DEBUG, "Using AVX2 Vector Tx (port %d).",
-- 
2.34.1