> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Ben Pfaff > Sent: Tuesday, 13 June, 2017 00:29 > To: [email protected] > Cc: Ben Pfaff <[email protected]> > Subject: [ovs-dev] [PATCH 11/31] fixup: Wrap docs to 79 columns. > > Also, OVS really supports the packet-type field in any version, since it > accepts OXM even in OpenFlow 1.0.
How does that relate to your earlier fixup (2/31) to make packet_type available only in OF1.5? Perhaps we misunderstand the semantics of the annotations in meta-flow.h. Are they just for documentation? > > Signed-off-by: Ben Pfaff <[email protected]> > --- > vswitchd/vswitch.xml | 9 ++++----- > 1 file changed, 4 insertions(+), 5 deletions(-) > > diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml > index 829c13688f31..299c6817c283 100644 > --- a/vswitchd/vswitch.xml > +++ b/vswitchd/vswitch.xml > @@ -857,11 +857,10 @@ > > <column name="other_config" key="packet-type-aware" > type='{"type": "boolean"}'> > - If set to <code>true</code>, the bridge supports the packet type > awareness > - feature introduced in OpenFlow version 1.5. The bridge can switch > Ethernet > - and non-Ethernet packets and a controller must consider the type and > match > - on the packet_type match field as appropriate. OVS does support the > packet- > - type-aware property from OpenFlow version 1.3. > + If set to <code>true</code>, the bridge supports the packet type > + awareness feature introduced in OpenFlow version 1.5. The bridge can > + switch Ethernet and non-Ethernet packets and a controller must > consider > + the type and match on the packet_type match field as appropriate. > </column> > > <column name="protocols"> > -- > 2.10.2 > > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
