Re: [dpdk-dev] [PATCH 0/3] fix invalid Tx threshhold setup

> -Original Message- > From: Xing, Beilei > Sent: Wednesday, May 15, 2019 2:36 PM > To: Zhang, Qi Z ; Lu, Wenzhuo > ; Yang, Qiming ; Ananyev, > Konstantin > Cc: dev@dpdk.org > Subject: RE: [PATCH 0/3] fix invalid Tx threshhold setup > > > > > -Original Message- > > From: Zhan

Re: [dpdk-dev] [PATCH 0/3] fix invalid Tx threshhold setup

> -Original Message- > From: Zhang, Qi Z > Sent: Saturday, May 4, 2019 5:30 PM > To: Xing, Beilei ; Lu, Wenzhuo > ; Yang, Qiming ; Ananyev, > Konstantin > Cc: dev@dpdk.org; Zhang, Qi Z > Subject: [PATCH 0/3] fix invalid Tx threshhold setup > > When tx_free_thresh + tx_rs_thresh > nb_d

[dpdk-dev] [PATCH 0/3] fix invalid Tx threshhold setup

When tx_free_thresh + tx_rs_thresh > nb_desc, it is possible that an outdated DD status be checked as tx_next_dd, then segment fault happen due to free a NULL mbuf pointer. The issue usually happens with an aggresive tx_free_thresh, for example: ./testpmd -c 0x3 -n 4 -- -i --rxq=16 --txq=16 --rxd