On Mon, Sep 19, 2016 at 03:52:25PM +0200, Christian Ehrhardt wrote: > On Mon, Sep 19, 2016 at 3:29 PM, Bruce Richardson < > bruce.richardson at intel.com> wrote: > > > > This patch set fixes problem when mbufs are not released back to the > > > original memory pool during Rx queue relese call leading to mbufs > > > "leakage". > > > > > > This issue happens when device stop (rte_eth_dev_stop()) will be called > > > after device start (rte_eth_dev_start()) without any incoming packets > > > received since device start. In this case both rxq->rx_tail and > > > rxq->rxrearm_start equal to 0 and release cycle will not be executed. > > > On the next device start (rte_eth_dev_start()) new set of mbufs for the > > > RX queue will be allocated. > > > > > > Yury Kylulin (2): > > > net/ixgbe: fix mbufs leakage during Rx queue release > > > net/i40e: fix mbufs leakage during Rx queue release > > > > > Applied to dpdk-next-net/rel_16_11 > > > > I don't know the underlying code well enough,
Me, neither. > but given the description I'd > expect that qualifies for the stable tree? But, yes, I agree with Christian. > Set stable at dpdk on cc. Thanks for doing that. --yliu