thx for your kind reply!<br/>While, i know that the openflow spec states it
undefined, but how does ovs implement it?<br/>And using the priority explicitly
seems like a dumb way in CIDR, isn't it?
At 2015-03-17 00:07:03, "Justin Pettit" <jpet...@nicira.com> wrote:
>
>> On Mar 16, 2015, at 12:32 AM, 张晨 <zhangchen9...@126.com> wrote:
>>
>> hello, dear all!
>>
>> Openflow spec doesn't specify how to direct flow entry with the same
>> priority and match fields to be selected. For example, i have an entry for
>> 1.0.0.0/24, and another for 1.0.0.1/32 with all the other fields the
>> same(priority same, too), how should these two entry be selected in ovs?
>> Apparently, i hope the second to be matched. Or only the priority field
>> could save me?
>
>The OpenFlow spec explicitly states that it's undefined:
>
> If there are multiple matching flow entries with the same highest
> priority, the selected flow entry is explicitly undefined.
>
>I wouldn't make assumption about how OVS chooses one, so just make it explicit
>by setting priorities.
>
>--Justin
>
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
