[ovs-discuss] c

[Charlie Li]

I don't think so - "ps -ef" shows the following processes

root      1458     1  0 16:17 ?        00:00:00 ./ovsdb-server
--remote=punix:/usr/local/var/run/openvswitch/db.sock --remote=db:Open_vSw
root      1464     1  0 16:18 ?        00:00:09 ./ovs-vswitchd --dpdk -c
0x1 -n 4 -- unix:/usr/local/var/run/openvswitch/db.sock --pidfil
root      1468  1332  0 16:19 pts/0    00:00:00 sudo ./ovs-vsctl add-br br0
-- set bridge br0 datapath_type=netdev
root      1469  1468  0 16:19 pts/0    00:00:00 ./ovs-vsctl add-br br0 --
set bridge br0 datapath_type=netdev


On Fri, Jul 1, 2016 at 4:38 PM, Ben Pfaff <blp at ovn.org> wrote:

> Does ovs-vswitchd die when you run that?
>
> On Fri, Jul 01, 2016 at 04:24:15PM -0500, Charlie Li wrote:
> > If I don't re-build DPDK and OVS, the following command will hang
> >
> > sudo ./ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev
> >
> > Looks like Bala reported the same issue (not sure if it is caused by the
> > same reason - not re-building OVS/DPDK)
> >
> > On Fri, Jul 1, 2016 at 3:21 PM, Ben Pfaff <blp at ovn.org> wrote:
> >
> > > On Fri, Jul 01, 2016 at 01:57:38PM -0500, Charlie Li wrote:
> > > > By now I am successful in running openvswitch-2.5.0 with DPDK-2.2.0
> by
> > > > following "INSTALL.DPDK.md <http://install.dpdk.md/>".
> > > >
> > > > I understand that I have to build DPDK and OVS for the very first
> time.
> > > >
> > > > # Build DPDK
> > > > cd $DPDK_DIR
> > > > make install T=x86_64-native-linuxapp-gcc
> > > >
> > > > # Configure & build OVS
> > > > cd $OVS_DIR
> > > > ./boot.sh
> > > > ./configure --with-dpdk=$DPDK_BUILD/
> > > > make CFLAGS='-O3 -march=native'
> > > >
> > > > But why do I have to build DPDK and OVS every time to run OVS-DPDK?
> > >
> > > You don't.  This doesn't make any sense.
> > >
> > > If you don't re-build OVS after you reboot, what happens?
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160701/962dd1c9/attachment-0002.html>