On Wed, Jun 15, 2011 at 1:15 PM, Ben Pfaff <b...@nicira.com> wrote: > On Tue, Jun 14, 2011 at 08:03:38AM -0700, Peter Phaal wrote: >> The porting guide shows an "ofproto provider" block in the first diagram, >> which I take to be the ofproto plugin? This block is dropped in the second >> diagram. > > The block labeled ofproto-dpif in the second diagram is an example of > an ofproto provider; that is, "ofproto provider" is the interface and > "ofproto-dpif" is one implementation of it. > > (Is there a good way to illustrate that in the diagrams? I can see > why it is confusing, but I don't yet see how to improve it.)
The text does make the point that ofproto-dpif is an implementation of "ofproto provider" - I wasn't reading carefully enough. How about this for the second diagram? 190 _ 191 | +-------------------+ 192 | | ovs-vswitchd |<-->ovsdb-server 193 | +-------------------+ 194 | | ofproto |<-->OpenFlow controllers 195 | +--------+-+--------+ _ 196 | | netdev | |ofproto-| | 197 userspace | +--------+ | dpif | | 198 | | netdev | +--------+ | 199 | |provider| | dpif | | 200 | +---||---+ +--------+ | 201 | || | dpif | | ofproto provider 202 | || |provider| | 203 |_ || +---||---+ | 204 || || | 205 _ +---||-----+---||---+ | 206 | | |datapath| | 207 kernel | | +--------+ _| 208 | | | 209 |_ +--------||---------+ 210 || 211 physical 212 NIC In case formatting doesn't come through clearly, the diagram includes a bracket on the right to indicate that the ofproto-dpif, dpif, dpif-provider and datapath together form an implementation of an ofproto provider. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
