On the first point - it's a little more subtle than that. A traffic flow (eg, a connection) must arrive at OVS, the first packet is sent through userspace, which causes userspace to install a megaflow into the datapath. Subsequently, if any traffic which matches that megaflow arrives, it will directly 'hit' the megaflow entry and execute the associated actions without going to userspace. Typically we use "microflow" to refer to a packet headers description which exact-matches all known fields, while "megaflow" allows a mask to be applied in addition to this, which allows the traffic which would otherwise be handled by multiple microflows to instead be handled by a single megaflow. There is no dependency between megaflows and microflows.
Cheers, Joe _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss