[ovs-dev] [PATCH 05/16] ofproto: Allow actions richer matches based on actions

2013-02-06 Thread Simon Horman
If the actions of a flow allow further decoding of L3 and L4 data to provide a richer match then use this richer match. For example: In the case of MPLS, L3 and L4 information may not initially be decoded from the frame as the ethernet type of the frame is an MPLS type and no information is known

[ovs-dev] [PATCH 05/16] ofproto: Allow actions richer matches based on actions

2013-02-06 Thread Simon Horman
If the actions of a flow allow further decoding of L3 and L4 data to provide a richer match then use this richer match. For example: In the case of MPLS, L3 and L4 information may not initially be decoded from the frame as the ethernet type of the frame is an MPLS type and no information is known

[ovs-dev] [PATCH 05/16] ofproto: Allow actions richer matches based on actions

2013-01-24 Thread Simon Horman
If the actions of a flow allow further decoding of L3 and L4 data to provide a richer match then use this richer match. For example: In the case of MPLS, L3 and L4 information may not initially be decoded from the frame as the ethernet type of the frame is an MPLS type and no information is known

[ovs-dev] [PATCH 05/16] ofproto: Allow actions richer matches based on actions

2013-01-17 Thread Simon Horman
If the actions of a flow allow further decoding of L3 and L4 data to provide a richer match then use this richer match. For example: In the case of MPLS, L3 and L4 information may not initially be decoded from the frame as the ethernet type of the frame is an MPLS type and no information is known

[ovs-dev] [PATCH 05/16] ofproto: Allow actions richer matches based on actions

2013-01-07 Thread Simon Horman
If the actions of a flow allow further decoding of L3 and L4 data to provide a richer match then use this richer match. For example: In the case of MPLS, L3 and L4 information may not initially be decoded from the frame as the ethernet type of the frame is an MPLS type and no information is known