X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=PORTING;h=3b3e150523db3b5fe200d01f23019b0a58a5f0fd;hb=abfec865566e6cce961cc8660de1ddfdc85dae5f;hp=516da8905a2204e96246c38224d03f99571640e6;hpb=0acc0c98860a75e17a2bcf4538f295dbe14cc1f1;p=openvswitch

diff --git a/PORTING b/PORTING
index 516da890..3b3e1505 100644
--- 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
@@ -202,6 +202,13 @@ during a port:
       vSwitch datapath module for the Linux kernel.  They may serve as
       a model for minimal netdev implementations.
 
+Miscellaneous Notes
+-------------------
+
+lib/uuid.c, used in OVSDB, assumes that it can obtain a high-quality
+random number seed at startup by reading from /dev/urandom.  You may
+need to modify it if this is not true on your platform.
+
 Questions
 ---------