I used the igb_uio, not the vfio-pci. and, when i bind the vfio , error like this: [root@node-4 ~]# modprobe vfio-pci [root@node-4 ~]# dpdk-devbind --bind=vfio-pci eth2 Error: bind failed for 0000:20:00.1 - Cannot bind to driver vfio-pci Error: unbind failed for 0000:20:00.1 - Cannot open /sys/bus/pci/drivers//unbind
在 2017-11-09 20:46:37，"Flavio Leitner" <[email protected]> 写道： >On Thu, 9 Nov 2017 18:07:05 +0800 (CST) >王嵘 <[email protected]> wrote: > >> hi, >> I rpmbuild the ovs-dpdk by myself, and the "config/common_base" : >> CONFIG_RTE_LIBRTE_BNX2X_PMD=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y >> CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y >> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y >> >> then ,I build the rpm of dpdk/dpdk-devel，and installed the 2 rpms to >> rpmbuild the ovs-dpdk。 >> when I used the ovs-dpdk with the bcm-NIC, there comes the error： >> >> here is the error in "/var/log/openvswitch/ovs-vswitchd.log" >> 2017-11-09T09:28:30.038Z|16773336|dpdk|INFO|EAL: PCI device 0000:20:00.1 on >> NUMA socket 0 >> 2017-11-09T09:28:30.038Z|16773337|dpdk|INFO|EAL: probe driver: 14e4:168e >> net_bnx2x >> 2017-11-09T09:28:30.038Z|16773338|dpdk|WARN|EAL: Requested device >> 0000:20:00.1 cannot be used >> 2017-11-09T09:28:30.038Z|16773339|dpdk|ERR|EAL: Driver cannot attach the >> device (0000:20:00.1) >> 2017-11-09T09:28:30.038Z|16773340|netdev_dpdk|WARN|Error attaching device >> '0000:20:00.1' to DPDK >> 2017-11-09T09:28:30.038Z|16773341|netdev|WARN|dpdk-eth2: could not set >> configuration (Invalid argument) > > >Looks like DPDK has the pmd enabled and has identified the device. >Did you bind the NIC to the VFIO driver before start OVS? > > >> And, my NIC firmware is : >> [root@node-4 ~]# ethtool -i eth2 >> driver: bnx2x >> version: 1.712.30-0 >> firmware-version: bc 7.0.49 >> expansion-rom-version: >> bus-info: 0000:20:00.1 >> supports-statistics: yes >> supports-test: yes >> supports-eeprom-access: yes >> supports-register-dump: yes >> supports-priv-flags: yes >> >> >> Does the fm version not satisfies ? or some other reasons ? > >I don't know about FW versions. >fbl > > >> >> >> >> >> >> >> 在 2017-11-08 21:28:01，"Flavio Leitner" <[email protected]> 写道： >> >On Wed, 8 Nov 2017 11:15:00 +0800 (CST) >> >王嵘 <[email protected]> wrote: >> > >> >> For now, I 'm using the "NetXtreme II BCM57810 10 Gigabit Ethernet 168e". >> >> Another question, I found ovs-dpdk can't bind this NIC. But I find >> >> there is the support code for 57810 in the DPDK Bnx2x. >> >> I'm puzzled. >> >> Can you tell me whether ovs-dpdk support this NIC? >> >> >> >> Thanks very much! >> > >> >You need to check that with your software provider. If you compiled >> >manually, then you need to check the options/config used to build DPDK. >> > >> >fbl >> > >> > >> >> 在 2017-11-08 09:11:25，"Ben Pfaff" <[email protected]> 写道： >> >> >On Tue, Nov 07, 2017 at 03:49:06PM +0800, 王嵘 wrote: >> >> >> Hi, >> >> >> I'm using ovs-dpdk（ovs2.8/dpdk17.05.2), and I want to use the offload >> >> >> feature. But I dont know how to enable it? >> >> >> As is represented in the release note 2.8: >> >> >> >> >> >> - Addexperimental support for hardware offloading >> >> >> * HW offloading is disabled by default. >> >> >> >> >> >> * HW offloading is done through the TC interface. >> >> > >> >> >Do you have a supported NIC? This feature is currently for a particular >> >> >model of Mellanox NICs. >> > >> > >> > >> >-- >> >Flavio >> > > > > >-- >Flavio >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
