On Jul 23, 2012, at 6:46 PM, chenzh wrote: > ->I can't find any clues about it from the newest openflow switch > specification(version 1.1). > Sorry I typed wrongly, Its v1.3. > Plus do you mean the following description: > 5.11: > The semantics of the action list is identical to the OpenFlow 1.0 > specication. The actions of an action list are executed in the order specied > by the list, and are applied immediately to the packet.
OVS doesn't support later versions of OpenFlow right now, so you'd need to look at the OpenFlow 1.0 spec. Here's the relevant part from section 3.3: -=-=-=-=-=-=-=-=- Each flow entry is associated with zero or more actions that dictate how the switch handles matching packets. If no forward actions are present, the packet is dropped. Action lists for inserted flow entries MUST be processed in the order specified. However, there is no packet output ordering guaranteed within a port. For example, an action list may result in two packets sent to two different VLANs on a single port. These two packets may be arbitrarily re-ordered, but the packet bodies must match those generated from a sequential execution of the actions. -=-=-=-=-=-=-=-=- Work is underway to support newer versions of OpenFlow, but it's not complete yet. --Justin _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
