diff options
author | Ethan Jackson <ethan@nicira.com> | 2011-11-18 19:00:34 -0800 |
---|---|---|
committer | Ethan Jackson <ethan@nicira.com> | 2011-11-21 10:36:46 -0800 |
commit | 82172632ad99204b58859edc93d5a76e63d4d73f (patch) | |
tree | 883c3f2bf52cb6c80b57a94a48b53053785e0eb0 /DESIGN | |
parent | 5fe0ec3dfc8c9006f98a98026ad2844440f5704b (diff) | |
download | openvswitch-82172632ad99204b58859edc93d5a76e63d4d73f.tar.gz |
ofp-util: Support OFPP_LOCAL in enqueue actions.
According to the specification the enqueue action should refer to
"a valid physical port", or OFPP_IN_PORT. It would be strange to
attach a queueing discipline to the local port, but I see no reason
to restrict it.
Diffstat (limited to 'DESIGN')
-rw-r--r-- | DESIGN | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -9,6 +9,16 @@ successful deployment. The end of this document contains contact information that can be used to let us know how we can make Open vSwitch more generally useful. +OpenFlow +======== + +The OpenFlow 1.0 specification requires the output port of the OFPAT_ENQUEUE +action to "refer to a valid physical port (i.e. < OFPP_MAX) or OFPP_IN_PORT". +Although OFPP_LOCAL is not less than OFPP_MAX, it is an 'internal' port which +can have QoS applied to it in Linux. Since we allow the OFPAT_ENQUEUE to apply +to 'internal' ports whose port numbers are less than OFPP_MAX, we interpret +OFPP_LOCAL as a physical port and support OFPAT_ENQUEUE on it as well. + Multiple Table Support ====================== |