X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=FAQ;h=2912ae335d1abdb9e5ae5e39ff586a7058da7200;hb=f263172c99fd0a72c3f6666ffbaeaab786a3f1a8;hp=ffe63cc0757b29577461d0ef2119e84ad07e1b15;hpb=d9cb84ff55c20c8503eec165071c03b206449390;p=sliver-openvswitch.git

diff --git a/FAQ b/FAQ
index ffe63cc07..2912ae335 100644
--- a/FAQ
+++ b/FAQ
@@ -418,7 +418,11 @@ A: First, why do you want to do this?  Two connected bridges are not
    ports will not work with the userspace datapath, only with the
    kernel module.
 
-Q: Why are there so many different ways to dump flows?
+
+Implementation Details
+----------------------
+
+Q: I hear OVS has a couple of kinds of flows.  Can you tell me about them?
 
 A: Open vSwitch uses different kinds of flows for different purposes:
 
@@ -446,7 +450,15 @@ A: Open vSwitch uses different kinds of flows for different purposes:
         current version of Open vSwitch, hardware switch
         implementations do not necessarily use this architecture.
 
-  Each of the commands for dumping flows has a different purpose:
+   Users and controllers directly control only the OpenFlow flow
+   table.  Open vSwitch manages the datapath flow table itself, so
+   users should not normally be concerned with it.
+
+Q: Why are there so many different ways to dump flows?
+
+A: Open vSwitch has two kinds of flows (see the previous question), so
+   it has commands with different purposes for dumping each kind of
+   flow:
 
       - "ovs-ofctl dump-flows <br>" dumps OpenFlow flows, excluding
         hidden flows.  This is the most commonly useful form of flow