> -----Original Message-----
> From: Wu, Jingjing <[email protected]>
> Sent: Wednesday, November 11, 2020 1:16 PM
> To: Xu, Ting <[email protected]>; [email protected]
> Cc: Zhang, Qi Z <[email protected]>; Xing, Beilei <[email protected]>;
> [email protected]
> Subject: RE: [PATCH v1] net/iavf: fix cannot release mbufs issue
>
>
>
> > -----Original Message-----
> > From: Xu, Ting <[email protected]>
> > Sent: Wednesday, November 11, 2020 11:07 AM
> > To: [email protected]
> > Cc: Zhang, Qi Z <[email protected]>; Xing, Beilei
> > <[email protected]>; Wu, Jingjing <[email protected]>; Xu,
> > Ting <[email protected]>; [email protected]
> > Subject: [PATCH v1] net/iavf: fix cannot release mbufs issue
> >
> > In the function _iavf_rx_queue_release_mbufs_vec to release rx mbufs,
> > rxq->rxrearm_nb is given the value of rx descriptor number at last.
> > However, since the process to release and allocate mbufs lacks the
> > initialization of rxrearm_nb, if we try to release mbufs next time, it
> > will return without releasing directly. In this patch, rxrearm_nb is
> > initialized to be zero in rx queue reset.
> >
> > Fixes: 319c421f3890 ("net/avf: enable SSE Rx Tx")
> > Cc: [email protected]
> >
> > Signed-off-by: Ting Xu <[email protected]>
>
> Acked-by: Jingjing Wu <[email protected]>
Applied to dpdk-next-net-intel.
Thanks
Qi
>
