[ovs-dev] [PATCH] Update userspace datapath documentation.

Jesse Gross jesse at nicira.com
Thu Mar 4 18:56:53 UTC 2010


Thanks, I pushed it.

On Thu, Mar 4, 2010 at 12:55 PM, Ben Pfaff <blp at nicira.com> wrote:

> Looks good.
>
> Thank you, Jesse.
>
> On Thu, Mar 04, 2010 at 01:17:03AM -0500, Jesse Gross wrote:
> > ---
> >  INSTALL.userspace |   22 ++++++++++++----------
> >  1 files changed, 12 insertions(+), 10 deletions(-)
> >
> > diff --git a/INSTALL.userspace b/INSTALL.userspace
> > index 241d79c..c13365a 100644
> > --- a/INSTALL.userspace
> > +++ b/INSTALL.userspace
> > @@ -34,28 +34,30 @@ then create /dev/net (if necessary) with "mkdir
> /dev/net", then create
> >  Using the Userspace Datapath with ovs-vswitchd
> >  ----------------------------------------------
> >
> > -To use ovs-vswitchd in userspace mode, give the bridge a name that
> > -begins with "netdev:" in the configuration file.  For example:
> > +To use ovs-vswitchd in userspace mode, create a bridge with
> datapath_type
> > +"netdev" in the configuration database.  For example:
> >
> > -    bridge.netdev:br0.port=eth0
> > -    bridge.netdev:br0.port=eth1
> > -    bridge.netdev:br0.port=eth2
> > +    ovs-vsctl add-br br0
> > +    ovs-vsctl set bridge br0 datapath_type=netdev
> > +    ovs-vsctl add-port br0 eth0
> > +    ovs-vsctl add-port br0 eth1
> > +    ovs-vsctl add-port br0 eth2
> >
> >  ovs-vswitchd will create a TAP device as the bridge's local interface,
> > -named the same as the bridge minus the "netdev:" prefix, as well as
> > -for each configured internal interface.
> > +named the same as the bridge, as well as for each configured internal
> > +interface.
> >
> >  Using the Userspace Datapath with ovs-openflowd
> >  -----------------------------------------------
> >
> >  To use ovs-openflowd in userspace mode, specify a datapath name that
> > -begins with "netdev:", and specify --ports with the names of the ports
> > +begins with "netdev@", and specify --ports with the names of the ports
> >  that should be included in the datapath as argument.  For example:
> >
> > -    ovs-openflowd netdev:br0 --ports=eth0,eth1,eth2
> > +    ovs-openflowd netdev at br0 --ports=eth0,eth1,eth2
> >
> >  ovs-openflowd will create a TAP device as the bridge's local
> > -interface, named the same as the bridge minus the "netdev:" prefix.
> > +interface, named the same as the bridge minus the "netdev@" prefix.
> >
> >  Bug Reporting
> >  -------------
> > --
> > 1.6.3.3
> >
> >
> > _______________________________________________
> > dev mailing list
> > dev at openvswitch.org
> > http://openvswitch.org/mailman/listinfo/dev_openvswitch.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-dev/attachments/20100304/72b0ae4e/attachment-0003.html>


More information about the dev mailing list