- The "wdp" branch has a software architecture that can take
advantage of hardware with support for wildcards (e.g. TCAMs or
- similar). This branch has known important bugs.
+ similar). This branch has known important bugs, but is the basis
+ of a few ongoing hardware projects, so we expect the quality to
+ improve rapidly.
-Since its architecture is better, in the medium to long term we hope
-to fix the problems in the "wdp" branch and merge it into "master".
+Since its architecture is better, in the medium to long term we will
+fix the problems in the "wdp" branch and merge it into "master".
In porting OVS, the major difference between the two branches is the
form of the flow table in the datapath:
useful examples during a port:
* lib/dpif-linux.c is a Linux-specific dpif implementation that
- talks to a Open vSwitch-specific kernel module (whose sources
+ talks to an Open vSwitch-specific kernel module (whose sources
are in the "datapath" directory). The kernel module performs
all of the switching work, passing packets that do not match any
- flow table entry down to userspace. This dpif implementation is
+ flow table entry up to userspace. This dpif implementation is
essentially a wrapper around calls to "ioctl".
* lib/dpif-netdev.c is a generic dpif implementation that performs
vSwitch datapath module for the Linux kernel. They may serve as
a model for minimal netdev implementations.
+Miscellaneous Notes
+-------------------
+
+lib/entropy.c assumes that it can obtain high-quality random number
+seeds at startup by reading from /dev/urandom. You will need to
+modify it if this is not true on your platform.
+
Questions
---------
git://git.onelab.eu / sliver-openvswitch.git / blobdiff