Re: [dpdk-dev] Problems running netvsc multiq

2018-12-08 Thread Mohammed Gamal
On Fri, 2018-12-07 at 11:18 -0800, Stephen Hemminger wrote: > On Fri, 07 Dec 2018 13:15:43 +0200 > Mohammed Gamal wrote: > > > On Wed, 2018-12-05 at 14:32 -0800, Stephen Hemminger wrote: > > > The problem is a regression in 4.20 kernel. Bisecting now.   > > > > I was bisecting the kernel and the

Re: [dpdk-dev] Problems running netvsc multiq

2018-12-07 Thread Stephen Hemminger
On Fri, 07 Dec 2018 13:15:43 +0200 Mohammed Gamal wrote: > On Wed, 2018-12-05 at 14:32 -0800, Stephen Hemminger wrote: > > The problem is a regression in 4.20 kernel. Bisecting now. > > I was bisecting the kernel and the change that seems to introduce this > regression is this one: > > commit

Re: [dpdk-dev] Problems running netvsc multiq

2018-12-07 Thread Stephen Hemminger
On Fri, 07 Dec 2018 13:15:43 +0200 Mohammed Gamal wrote: > On Wed, 2018-12-05 at 14:32 -0800, Stephen Hemminger wrote: > > The problem is a regression in 4.20 kernel. Bisecting now. > > I was bisecting the kernel and the change that seems to introduce this > regression is this one: > > commit

Re: [dpdk-dev] Problems running netvsc multiq

2018-12-07 Thread Mohammed Gamal
On Wed, 2018-12-05 at 14:32 -0800, Stephen Hemminger wrote: > The problem is a regression in 4.20 kernel. Bisecting now. I was bisecting the kernel and the change that seems to introduce this regression is this one: commit ae6935ed7d424ffa74d634da00767e7b03c98fd3 Author: Stephen Hemminger Date: 

Re: [dpdk-dev] Problems running netvsc multiq

2018-12-05 Thread Stephen Hemminger
The problem is a regression in 4.20 kernel. Bisecting now. The kernel in 4.19.7 works. Failure with logging is: $ sudo ./testpmd -l 0-1 -n2 --log-level=8 --log-level='pmd.*,8' --log-level='bus.vmbus,8' -- --port-topology=chained --forward-mode=rxonly --stats-period 1 --eth-peer=0,00:15:5d:1e:20

Re: [dpdk-dev] Problems running netvsc multiq

2018-12-05 Thread Stephen Hemminger
On WS2016 and 4.19.7 kernel (with the 4 patches), this is what I see: $ sudo ./testpmd -l 0-1 -n2 --log-level=8 --log-level='pmd.*,8' --log-level='bus.vmbus,8' -- --port-topology=chained --forward-mode=rxonly --stats-period 1 --eth-peer=0,00:15:5d:1e:20:c0 --txq 2 --rxq 2 EAL: Detected 4 lcore(s

Re: [dpdk-dev] Problems running netvsc multiq

2018-12-04 Thread Mohammed Gamal
On Tue, 2018-12-04 at 08:48 -0800, Stephen Hemminger wrote: > On Fri, 30 Nov 2018 14:06:52 -0500 (EST) > Mohammed Gamal wrote: > > > - Stephen Hemminger wrote: > > > On Fri, 30 Nov 2018 12:04:41 +0100 > > > Mohammed Gamal wrote: > > >    > > > > Hi All, > > > > I am having the following err

Re: [dpdk-dev] Problems running netvsc multiq

2018-12-04 Thread Stephen Hemminger
On Fri, 30 Nov 2018 14:06:52 -0500 (EST) Mohammed Gamal wrote: > - Stephen Hemminger wrote: > > On Fri, 30 Nov 2018 12:04:41 +0100 > > Mohammed Gamal wrote: > > > > > Hi All, > > > I am having the following errors when I run testpmd with the netvsc > > > driver and --txq 2 and --rxq 2 op

Re: [dpdk-dev] Problems running netvsc multiq

2018-11-30 Thread Mohammed Gamal
- Stephen Hemminger wrote: > On Fri, 30 Nov 2018 12:04:41 +0100 > Mohammed Gamal wrote: > > > Hi All, > > I am having the following errors when I run testpmd with the netvsc > > driver and --txq 2 and --rxq 2 options: > > > > testpmd: create a new mbuf pool : n=155456, > > size=2176, sock

Re: [dpdk-dev] Problems running netvsc multiq

2018-11-30 Thread Stephen Hemminger
On Fri, 30 Nov 2018 12:04:41 +0100 Mohammed Gamal wrote: > Hi All, > I am having the following errors when I run testpmd with the netvsc > driver and --txq 2 and --rxq 2 options: > > testpmd: create a new mbuf pool : n=155456, > size=2176, socket=0 > testpmd: preferred mempool ops selected: ring

[dpdk-dev] Problems running netvsc multiq

2018-11-30 Thread Mohammed Gamal
Hi All, I am having the following errors when I run testpmd with the netvsc driver and --txq 2 and --rxq 2 options: testpmd: create a new mbuf pool : n=155456, size=2176, socket=0 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 0 (socket 0) hn_dev_configure():  >> hn_rndis_lin