Prepare Open vSwitch 1.1.2 release.

[sliver-openvswitch.git] / PORTING

diff --git a/PORTING b/PORTING
index 516da89..911761e 100644 (file)
--- a/PORTING
+++ b/PORTING
@@ -127,10 +127,10 @@ There are two existing dpif implementations that may serve as
 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
@@ -197,10 +197,20 @@ during a port:
       network devices, using Linux kernel calls.  It may be a good
       place to start for full-featured netdev implementations.
 
-    * lib/netdev-gre.c and lib/netdev-patch.c are minimal
-      implementations for "virtual ports" implemented by the Open
-      vSwitch datapath module for the Linux kernel.  They may serve as
-      a model for minimal netdev implementations.
+    * lib/netdev-vport.c provides support for "virtual ports" 
+      implemented by the Open vSwitch datapath module for the Linux
+      kernel.  This 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.
+
+vswitchd/system-stats.c only knows how to obtain some statistics on
+Linux.  Optionally you may implement them for your platform as well.
 
 Questions
 ---------