RE: [PATCH v3] net/iavf: fix mbuf release API selection

ou, > > YidingX ; Deng, KaiwenX > > ; Wu, Jingjing ; Xing, > > Beilei ; Zeng, ZhichaoX > > > > Subject: RE: [PATCH v3] net/iavf: fix mbuf release API selection > > > > > > > > > -Original Message- > > > From: Kaiwen Deng >

RE: [PATCH v3] net/iavf: fix mbuf release API selection

> > ; Wu, Jingjing ; Xing, > > Beilei ; Zeng, ZhichaoX > > > > Subject: [PATCH v3] net/iavf: fix mbuf release API selection > > > > When AVX2 is forcibly selected and outer checksum offload is > > configured, the basic Tx path will be selected. Also, the tx

RE: [PATCH v3] net/iavf: fix mbuf release API selection

> -Original Message- > From: Kaiwen Deng > Sent: Thursday, November 2, 2023 12:43 PM > To: dev@dpdk.org > Cc: sta...@dpdk.org; Yang, Qiming ; Zhou, YidingX > ; Deng, KaiwenX ; Wu, > Jingjing ; Xing, Beilei ; Zeng, > ZhichaoX > Subject: [PATCH v3] net

[PATCH v3] net/iavf: fix mbuf release API selection

When AVX2 is forcibly selected and outer checksum offload is configured, the basic Tx path will be selected. Also, the txq mbuf release API is incorrectly set to iavf_tx_queue_release_mbufs_sse. This causes coredump. This commit selects release_txq_mbufs to releasing txq mbufs when selecting the b