Hi, OVS works nicely with DPDK. you can follow the same tutorial. http://openvswitch.org/support/dist-docs/INSTALL.DPDK.md.txt
As mentioned in the table before starting the vswitchd daemon, you need to bind the interfaces to dpdk. and then start the switchd as follows. 1. Bind the interface to dpdk something like this. ./tools/dpdk_nic_bind.py --bind=igb_uio ens2f0 ./tools/dpdk_nic_bind.py --bind=igb_uio ens2f1 ./tools/dpdk_nic_bind.py --status 2. Then start the OVS vswitchd : ovs-vswitchd --dpdk -c 0x1 -n 4 -- unix:$DB_SOCK --pidfile --detach 3. Create the bridge: ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev -- set bridge br0 protocols=OpenFlow13 4.Add the ports to switchd : ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk -- set interface dpdk0 ofport_request=1 ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk -- set interface dpdk1 ofport_request=2 *Note here*: 1. As mentioned the tutorial, OVS expects DPDK device names to start with "dpdk" and end with a portid. vswitchd should print (in the log file) the number of dpdk devices found. 2. And Type should be dpdk. So here its dpdk0 and dpdk1. I hope it will helps you. Regards, Beeru On Wed, Jan 20, 2016 at 3:30 PM, 许志峰 <zhifengx...@gmail.com> wrote: > Hello all, > I am using OVS-DPDK, following this tutorial > > https://github.com/01org/dpdk-ovs/blob/development/docs/04_Sample_Configurations/00_Phy-Phy.md > . > and I encountered some problems. > > I have two physical NICs binded to DPDK driver > > Network devices using DPDK-compatible driver > ============================================ > 0000:06:00.0 '82574L Gigabit Network Connection' drv=igb_uio > unused=vfio-pci > 0000:07:00.0 '82574L Gigabit Network Connection' drv=igb_uio > unused=vfio-pci > > Then I add a bridge br0 and 2 ports, follow the, just as the tutorial did. > and the ovs-vsctl show is normal. > > 170c321a-0dea-48c5-94dd-f53ec5587a44 > Bridge "br0" > Port "port2" > Interface "port2" > type: dpdkphy > options: {port="1"} > Port "port1" > Interface "port1" > type: dpdkphy > options: {port="0"} > Port "br0" > Interface "br0" > type: internal > > I start ovs-dpdk and it works well and Statistic info is printed. Then I > start vswitch by./vswitchd/ovs-vswitchd -c 0x100 --proc-type=secondary -- > --pidfile=/tmp/vswitchd.pid part of the output is > > 2016-01-16T09:20:40Z|00036|dpdk_link|INFO|Found OVDK03_Control_Alloc_Ring > 2016-01-16T09:20:40Z|00037|dpif_dpdk|ERR|Unable to successfully add IN > port to datapath, error '-19' > 2016-01-16T09:20:40Z|00038|dpif|WARN|dpdk@ovs-dpdk: failed to add > port1 as port: Unknown error -19 > 2016-01-16T09:20:40Z|00039|dpif_dpdk|ERR|Unable to successfully add IN > port to datapath, error '-19' > 2016-01-16T09:20:40Z|00040|dpif|WARN|dpdk@ovs-dpdk: failed to add > port2 as port: Unknown error -19 > 2016-01-16T09:20:40Z|00041|bridge|INFO|bridge br0: added interface br0 > on port 65534 > 2016-01-16T09:20:40Z|00042|bridge|INFO|bridge br0: using datapath ID > 000086f3dadf9c41 > 2016-01-16T09:20:40Z|00043|connmgr|INFO|br0: added service controller > "punix:/usr/local/var/run/openvswitch/br0.mgmt" > 2016-01-16T09:20:40Z|00044|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.1.2 > 2016-01-16T09:20:50Z|00045|memory|INFO|16588 kB peak resident set size > after 10.0 seconds > 2016-01-16T09:20:50Z|00046|memory|INFO|dispatchers:1 flow_dumpers:1 > handlers:5 ports:1 revalidators:3 rules:4 > > I tried to use dpdk0/dpdk1 to replace port1/port2 and got the same error. > http://openvswitch.org/support/dist-docs/INSTALL.DPDK.md.txt step 6 > I also tried ovs_dpdk_16/17 because I saw the last page of this PDF > > https://01.org/sites/default/files/downloads/packet-processing/intel_dpdk_vswitch_gsg_0_7.pdf > > I found a same question here > https://lists.01.org/pipermail/dpdk-ovs/2014-May/000973.html > <https://lists.01.org/pipermail/dpdk-ovs/2014-May/000973.html> > the solution is to use the command below: > > ./utilities/ovs-vsctl --no-wait add-port br0 port16 -- set Interface > port16 type=dpdkphy ofport_request=16 option:port=1 > > > but the solution does not work for me. > > What interface name should I use? Or am I missing some something and how > can I fix this? > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
