The OpenFlow spec says packets shouldn't match against multiple flows
at the same priority or the result is undefined. In ovsfw, 8 priority
levels are needed to comply with this rule.
Note: unlike overlapping TCP port ranges cases, the current version
of OVS seems to handle this case magically.
Change-Id: I6deaee8dbe81453285b1fc685282952bc9456949
Closes-bug: #1708092
(cherry picked from commit 4ac4c22a646799aaecca61334a8bb44147ab881a)
Reviewed: https:/ /review. openstack. org/524533 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=5c16f2bd79e abc7f7a069d9af9 ff832dbdb4be54
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 5c16f2bd79eabc7 f7a069d9af9ff83 2dbdb4be54
Author: IWAMOTO Toshihiro <email address hidden>
Date: Thu Aug 17 15:13:53 2017 +0900
ovsfw: Use multiple priorities in RULES_*_TABLE
The OpenFlow spec says packets shouldn't match against multiple flows
at the same priority or the result is undefined. In ovsfw, 8 priority
levels are needed to comply with this rule.
Note: unlike overlapping TCP port ranges cases, the current version
of OVS seems to handle this case magically.
Change-Id: I6deaee8dbe8145 3285b1fc6852829 52bc9456949 aecca61334a8bb4 4147ab881a)
Closes-bug: #1708092
(cherry picked from commit 4ac4c22a646799a