[dpdk-dev] Under Ovs-2.8.0 + DPDK-17.05-rc1, can't add port which using mlx5 driver onto bridge br0

Sam batmanustc at gmail.com
Thu Mar 29 04:29:24 CEST 2018


KNI also works

2018-03-29 10:03 GMT+08:00 Sam <batmanustc at gmail.com>:

> But testpmd at the same version of DPDK is OK, like this:
>
> [gangyewei at yf-mos-test-net07 dpdk]$ sudo /usr/local/share/openvswitch/scripts/dpdk_nic_bind
>> --status
>> Network devices using DPDK-compatible driver
>> ============================================
>> <none>
>> Network devices using kernel driver
>> ===================================
>> ...
>> 0000:03:00.0 'MT27640 Family' if=eth4 drv=mlx5_core unused=igb_uio
>> 0000:03:00.1 'MT27640 Family' if=eth5 drv=mlx5_core unused=igb_uio
>> 0000:03:00.2 'MT27641 Family' if=enp3s0f2 drv=mlx5_core unused=igb_uio
>> *Active*
>> ...
>> =====================
>> <none>
>> [gangyewei at 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=2 - cores=1 - streams=2 - NUMA support
>> disabled, MP over anonymous pages disabled
>> Logical Core 18 (socket 0) forwards packets on 2 streams:
>>   RX P=0/Q=0 (socket 0) -> TX P=1/Q=0 (socket 0) peer=02:00:00:00:00:01
>>   RX P=1/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00
>>   mac packet forwarding - CRC stripping disabled - packets/burst=32
>>   nb forwarding cores=1 - nb forwarding ports=2
>>   RX queues=1 - RX desc=128 - RX free threshold=0
>>   RX threshold registers: pthresh=0 hthresh=0 wthresh=0
>>   TX queues=1 - TX desc=512 - TX free threshold=0
>>   TX threshold registers: pthresh=0 hthresh=0 wthresh=0
>>   TX RS bit threshold=0 - TXQ flags=0x0
>> testpmd>
>
>
> 2018-03-28 20:49 GMT+08:00 Nélio Laranjeiro <nelio.laranjeiro at 6wind.com>:
>
>> 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
>> > > ============================================
>> > > <none>
>> > > Network devices using kernel driver
>> > > ===================================
>> > > ...
>> > > 0000:03:00.0 'MT27640 Family' if=eth4 drv=mlx5_core unused=igb_uio
>> > > 0000:03:00.1 'MT27640 Family' if=eth5 drv=mlx5_core unused=igb_uio
>> > > 0000:03:00.2 'MT27641 Family' if=enp3s0f2 drv=mlx5_core unused=igb_uio
>> > > *Active*
>> > > ...
>> > > =====================
>> > > <none>
>> >
>> >
>> > When I start ovs-vswitchd, and add port onto br0, I got errors like
>> this:
>> >
>> > 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
>> on
>> > > 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
>> device
>> > > '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élio Laranjeiro
>> 6WIND
>>
>
>


More information about the dev mailing list