[dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is greater than 1"

2014-10-20 Thread Matthew Hall
On Mon, Oct 20, 2014 at 10:36:01AM +0100, Bruce Richardson wrote: > On Sun, Oct 19, 2014 at 10:08:29AM -0700, Matthew Hall wrote: > > 1.7.1 with a few minor clang compatibility patches in the example apps > > Rather than trying to tune the results yourself, maybe you could look to > merge in the

[dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is greater than 1"

2014-10-20 Thread Bruce Richardson
On Sun, Oct 19, 2014 at 10:08:29AM -0700, Matthew Hall wrote: > 1.7.1 with a few minor clang compatibility patches in the example apps Rather than trying to tune the results yourself, maybe you could look to merge in the following patch set also, to offload responsibility for the driver

[dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is greater than 1"

2014-10-19 Thread Marc Sune
Which DPDK version are you using marc On 19/10/14 00:50, Matthew Hall wrote: > Hello, > > I'm just trying to understand what you're supposed to do about this error to > get the optiomal configuration / performance. The error message and comments > seem like they're designed for Intel ethernet

[dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is greater than 1"

2014-10-19 Thread Matthew Hall
1.7.1 with a few minor clang compatibility patches in the example apps -- Sent from my mobile device. On October 19, 2014 6:46:27 AM PDT, Marc Sune wrote: >Which DPDK version are you using > >marc > >On 19/10/14 00:50, Matthew Hall wrote: >> Hello, >> >> I'm just trying to understand what

[dpdk-dev] "TX WTHRESH must be set to 0 if tx_rs_thresh is greater than 1"

2014-10-18 Thread Matthew Hall
Hello, I'm just trying to understand what you're supposed to do about this error to get the optiomal configuration / performance. The error message and comments seem like they're designed for Intel ethernet driver hackers not security hackers like myself! ;-) Note: I'm trying out the Intel