On Mar 9, 2013, at 16:54 , ext Simon Horman wrote: > It is not obvious to me how the behaviour relating to get_priority() as > described above can sensibly be reconciled with a desire to preserve the > order of actions. Or even reconciled with a looser constraint that actions > that need l3+ data occur before push_mpls actions.
Maybe do_xlate_actions() should take care of translating the skb_priority to nw_tos, and make sure that it happens before any L2.5 actions are translated. This would make any later set actions on skb_priority ineffective, though. Also, it seems that on the patch port output the nw_tos is not set, so that might require some further thought. Maybe it is of no functional use for the network transport, but still the peer might actually depend (via a match) on the nw_tos being set the same way as any other port might have it? Jarno _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
