From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Subject: Re: Under Ovs-2.8.0 + DPDK-17.05-rc1, can't add port which using mlx5 driver onto bridge br0 Date: Thu, 29 Mar 2018 10:03:31 +0800 Message-ID: References: <20180328124902.jhbwpax4ufx7yslp@laranjeiro-vm.dev.6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org To: =?UTF-8?Q?N=C3=A9lio_Laranjeiro?= Return-path: Received: from mail-qt0-f171.google.com (mail-qt0-f171.google.com [209.85.216.171]) by dpdk.org (Postfix) with ESMTP id 9D42A23D for ; Thu, 29 Mar 2018 04:03:32 +0200 (CEST) Received: by mail-qt0-f171.google.com with SMTP id f16so4775654qth.3 for ; Wed, 28 Mar 2018 19:03:32 -0700 (PDT) In-Reply-To: <20180328124902.jhbwpax4ufx7yslp@laranjeiro-vm.dev.6wind.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" But testpmd at the same version of DPDK is OK, like this: [gangyewei@yf-mos-test-net07 dpdk]$ sudo > /usr/local/share/openvswitch/scripts/dpdk_nic_bind --status > Network devices using DPDK-compatible driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Network devices using kernel driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > ... > 0000:03:00.0 'MT27640 Family' if=3Deth4 drv=3Dmlx5_core unused=3Digb_uio > 0000:03:00.1 'MT27640 Family' if=3Deth5 drv=3Dmlx5_core unused=3Digb_uio > 0000:03:00.2 'MT27641 Family' if=3Denp3s0f2 drv=3Dmlx5_core unused=3Digb_= uio > *Active* > ... > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > [gangyewei@yf-mos-test-net07 dpdk]$ sudo > x86_64-native-linuxapp-gcc/app/testpmd -c 0x40004 -n 4 -w 0000:03:00.0 -= w > 0000:03:00.1 -- -i > ... > EAL: Support maximum 128 logical core(s) by configuration. > EAL: Detected 32 lcore(s) > EAL: Probing VFIO support... > EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or > directory) > EAL: VFIO modules not loaded, skipping VFIO support... > EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or > directory) > EAL: Setting up physically contiguous memory... > ... > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > EAL: probe driver: 15b3:1017 net_mlx5 > EAL: PCI device 0000:03:00.1 on NUMA socket 0 > EAL: probe driver: 15b3:1017 net_mlx5 > Interactive-mode selected > Configuring Port 0 (socket 0) > Port 0: EC:0D:9A:8E:D0:9C > Configuring Port 1 (socket 0) > Port 1: EC:0D:9A:8E:D0:9D > Checking link statuses... > Port 0 Link Up - speed 10000 Mbps - full-duplex > Port 1 Link Up - speed 10000 Mbps - full-duplex > Done > testpmd> testpmd> set fwd mac > Set mac packet forwarding mode > testpmd> srat > Command not found > testpmd> start > mac packet forwarding - ports=3D2 - cores=3D1 - streams=3D2 - NUMA suppor= t > disabled, MP over anonymous pages disabled > Logical Core 18 (socket 0) forwards packets on 2 streams: > RX P=3D0/Q=3D0 (socket 0) -> TX P=3D1/Q=3D0 (socket 0) peer=3D02:00:00:= 00:00:01 > RX P=3D1/Q=3D0 (socket 0) -> TX P=3D0/Q=3D0 (socket 0) peer=3D02:00:00:= 00:00:00 > mac packet forwarding - CRC stripping disabled - packets/burst=3D32 > nb forwarding cores=3D1 - nb forwarding ports=3D2 > RX queues=3D1 - RX desc=3D128 - RX free threshold=3D0 > RX threshold registers: pthresh=3D0 hthresh=3D0 wthresh=3D0 > TX queues=3D1 - TX desc=3D512 - TX free threshold=3D0 > TX threshold registers: pthresh=3D0 hthresh=3D0 wthresh=3D0 > TX RS bit threshold=3D0 - TXQ flags=3D0x0 > testpmd> 2018-03-28 20:49 GMT+08:00 N=C3=A9lio Laranjeiro : > On Wed, Mar 28, 2018 at 08:20:00PM +0800, Sam wrote: > > Hi all, > > > > I'm using Ovs-2.8.0 + DPDK-17.05-rc1 with two netdev using mlx5 driver, > > like this: > > > > $ sudo /usr/local/share/openvswitch/scripts/dpdk_nic_bind --status > > > Network devices using DPDK-compatible driver > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > Network devices using kernel driver > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > ... > > > 0000:03:00.0 'MT27640 Family' if=3Deth4 drv=3Dmlx5_core unused=3Digb_= uio > > > 0000:03:00.1 'MT27640 Family' if=3Deth5 drv=3Dmlx5_core unused=3Digb_= uio > > > 0000:03:00.2 'MT27641 Family' if=3Denp3s0f2 drv=3Dmlx5_core unused=3D= igb_uio > > > *Active* > > > ... > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > > > > When I start ovs-vswitchd, and add port onto br0, I got errors like thi= s: > > > > libibverbs: Warning: no userspace device-specific driver found for > > > /sys/class/infiniband_verbs/uverbs2 > > > > > > and git errors in ovs-vswitchd.log like this: > > > > 2018-03-28T09:34:25.687Z|00120|dpdk|INFO|EAL: PCI device 0000:03:00.0 o= n > > > NUMA socket 0 > > > 2018-03-28T09:34:25.687Z|00121|dpdk|INFO|EAL: probe driver: > 15b3:1017 > > > net_mlx5 > > > 2018-03-28T09:34:25.687Z|00122|dpdk|WARN|EAL: Requested device > > > 0000:03:00.0 cannot be used > > > 2018-03-28T09:34:25.687Z|00123|dpdk|ERR|EAL: Driver cannot attach the > > > device (0000:03:00.0) > > > 2018-03-28T09:34:25.687Z|00124|netdev_dpdk|WARN|Error attaching devic= e > > > '0000:03:00.0' to DPDK > > > 2018-03-28T09:34:25.687Z|00125|netdev|WARN|dpdk0: could not set > > > configuration (Invalid argument) > > > > > > How to fix this bug? Is there anyone got these errors? Thank you~ > > Hi, > > I would say you don't have the correct Linux drivers, nor libraries to > make it work with DPDK. > Did you installed Mellanox OFED? If not take a look at section 19.5. > Prerequisites of the NIC documentation [1]. > > Regards, > > [1] https://dpdk.org/doc/guides-17.05/nics/mlx5.html > > -- > N=C3=A9lio Laranjeiro > 6WIND >