dpif-netdev: Store miniflow length in exact match cache

[cascardo/ovs.git] / FAQ

diff --git a/FAQ b/FAQ
index 79d905d..df5ac0e 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -520,6 +520,10 @@ A: Open vSwitch has two kinds of flows (see the previous question), so
         dumps datapath flows for only the specified bridge, regardless
         of the type.
 
+Q: How does multicast snooping works with VLANs?
+
+A: Open vSwitch maintains snooping tables for each VLAN.
+
 
 Performance
 -----------
@@ -587,7 +591,7 @@ A: A physical Ethernet device that is part of an Open vSwitch bridge
    versions of Linux that Open vSwitch supports.
 
    By the way, this issue is not specific to physical Ethernet
-   devices.  It applies to all network devices except Open vswitch
+   devices.  It applies to all network devices except Open vSwitch
    "internal" devices.
 
 Q: I created a bridge and added a couple of Ethernet ports to it,
@@ -1124,6 +1128,12 @@ A: Do you have a controller configured on br0 (as the commands above
    OpenFlow controller doesn't see the VLANs that I expect," and you
    can refer to the answer there for more information.
 
+Q: How MAC learning works with VLANs?
+
+A: Open vSwitch implements Independent VLAN Learning (IVL) for
+   OFPP_NORMAL action.  I.e. it logically has separate learning tables
+   for each VLANs.
+
 
 VXLANs
 -----
@@ -1229,12 +1239,14 @@ A: Before version 1.11, Open vSwitch did not support MPLS.  That is,
    packet.  Kernel datapath support is unchanged from earlier
    versions.
 
-   Open vSwitch version 2.2 will be able to match, push, or pop up to
-   3 MPLS labels.  Looking past MPLS labels into the encapsulated
-   packet will still be unsupported.  Both userspace and kernel
-   datapaths will be supported, but MPLS processing always happens in
-   userspace either way, so kernel datapath performance will be
-   disappointing.
+   Open vSwitch version 2.3 can match, push, or pop up to 3 MPLS
+   labels.  Looking past MPLS labels into the encapsulated packet will
+   still be unsupported.  Both userspace and kernel datapaths will be
+   supported, but MPLS processing always happens in userspace either
+   way, so kernel datapath performance will be disappointing.
+
+   Open vSwitch version 2.4 will have kernel support for MPLS,
+   yielding improved performance.
 
 Q: I'm getting "error type 45250 code 0".  What's that?