so the value is not necessarily meaningful. We might have to
just fix it as the same as in_port.
- * On OF1.1+ flow_mods, updates by MODIFY are now much better
- specified. Check that OVS implements the new behavior, fix it
- if not.
-
* OFPT_TABLE_MOD stats. This is new in OF1.1, so we need to
implement it. It should be implemented so that the default OVS
behavior does not change.
- * Document how OVS does packet buffering.
-
* MPLS. Simon Horman maintains a patch series that adds this
feature. This is partially merged.
OpenFlow 1.2 support requires OpenFlow 1.1 as a prerequisite, plus the
following additional work. (This is based on the change log at the
-end of the OF1.2 spec. I didn’t compare the specs carefully yet.)
-
- * Use new OpenFlow extensible error infrastructure, on OF1.2+
- only, instead of the OVS-specific extension used until now.
+end of the OF1.2 spec. I didn't compare the specs carefully yet.)
* OFPT_FLOW_MOD:
- * MODIFY and MODIFY_STRICT commands now never insert new flows
- in the table. We will still need variations that do,
- though, both to support older OpenFlow protocols and to get
- sensible behavior for the internal implementation of the
- NXAST_LEARN action.
-
* New flag OFPFF_RESET_COUNTS.
- * New cookie field behavior.
-
* Add ability to delete flow in all tables.
* Update DESIGN to describe OF1.2 behavior also.
- * Add ability to turn off packet buffering with OFPCML_NO_BUFFER.
-
OpenFlow 1.3
------------
OpenFlow 1.3 support requires OpenFlow 1.2 as a prerequisite, plus the
following additional work. (This is based on the change log at the
end of the OF1.3 spec, reusing most of the section titles directly. I
-didn’t compare the specs carefully yet.)
+didn't compare the specs carefully yet.)
* Add support for multipart requests.
and design requirements. Might be politically difficult to add
directly to the kernel module, since its functionality overlaps
with tc. Ideally, therefore, we could implement these somehow
- with tc, but I haven’t investigated whether that makes sense.
+ with tc, but I haven't investigated whether that makes sense.
* Per-connection event filtering. OF1.3 adopted Open vSwitch's
existing design for this feature so implementation should be
* Auxiliary connections. These are optional, so a minimal
implementation would not need them. An implementation in
- generic code might be a week’s worth of work. The value of an
+ generic code might be a week's worth of work. The value of an
implementation in generic code is questionable, though, since
much of the benefit of axuiliary connections is supposed to be
to take advantage of hardware support. (We could make the
kernel module somehow send packets across the auxiliary
- connections directly, for some kind of “hardware” support, if we
+ connections directly, for some kind of "hardware" support, if we
judged it useful enough.)
* MPLS BoS matching. (Included in Simon's MPLS series?)
- * Provider Backbone Bridge tagging. I don’t plan to implement
- this (but we’d accept an implementation).
+ * Provider Backbone Bridge tagging. I don't plan to implement
+ this (but we'd accept an implementation).
- * Rework tag order. I’m not sure whether we need to do anything
+ * Rework tag order. I'm not sure whether we need to do anything
for this.
- * Duration for stats.
+ * Duration for queue stats. (Duration for port stats is already
+ implemented.)
* On-demand flow counters. I think this might be a real
optimization in some cases for the software switch.
tree).
* The patch submission guidelines (see SubmittingPatches). I
- recommend using “git send-email”, which automatically follows a
+ recommend using "git send-email", which automatically follows a
lot of those guidelines.
Bug Reporting
git://git.onelab.eu / sliver-openvswitch.git / blobdiff