| | ovs-vswitchd |<-->ovsdb-server
| +-------------------+
| | ofproto |<-->OpenFlow controllers
- | +--------+-+--------+
- | | netdev | |ofproto-|
- userspace | +--------+ | dpif |
- | | netdev | +--------+
- | |provider| | dpif |
- | +---||---+ +--------+
- | || | dpif |
- | || |provider|
- |_ || +---||---+
- || ||
- _ +---||-----+---||---+
- | | |datapath|
- kernel | | +--------+
+ | +--------+-+--------+ _
+ | | netdev | |ofproto-| |
+ userspace | +--------+ | dpif | |
+ | | netdev | +--------+ |
+ | |provider| | dpif | |
+ | +---||---+ +--------+ |
+ | || | dpif | | implementation of
+ | || |provider| | ofproto provider
+ |_ || +---||---+ |
+ || || |
+ _ +---||-----+---||---+ |
+ | | |datapath| |
+ kernel | | +--------+ _|
| | |
|_ +--------||---------+
||
name makes the intended use obvious.
ovs-vswitchd is the most sophisticated of ofproto's clients, but
-ofproto can have other clients as well. ovs-openflowd, in the
-utilities directory, is much simpler than ovs-vswitchd. It may be
-easier to initially bring up ovs-openflowd as part of a port.
+ofproto can have other clients as well. test-openflowd, in the
+tests directory, is much simpler than ovs-vswitchd. It may be
+easier to initially bring up test-openflowd as part of a port.
lib/entropy.c assumes that it can obtain high-quality random number
seeds at startup by reading from /dev/urandom. You will need to