Alexander Wu (9):
  ofp-msgs: Fix limits of OFPMP_TABLE_FEATURES.
  ofp-util: Implement OFPMP_TABLE_FEATURES en/decode
  ofproto-provider: Add/Modify headers for OFPMP_TABLE_FEATURES in
    ofproto
  ofproto: handle OFPMP_TABLE_FEATURES msgs and its lifecycle.
  ofp-print: Implement the function to print OFPMP_TABLE_FEATURES
  ofctl: Add ovs-ofctl dump-table-features.
  rconn: Allow OFPMP_TABLE_FEATURES openflow messages.
  AT: Add tests for OFPMP_TABLE_FEATURES.
  ofp-actions: add func to get inst name by OpenFlow instruction type
    directly.

Patch-Description:
  This patch is to implement table features GET msg in openflow 1.3.
 
  The spec says:
   If the request body contains an array of one or more ofp_table_features
   structs, the switch will attempt to change its flow tables to match the
   requested flow table configuration. This operation configures the entire
   pipeline, and the set of flow tables in the pipeline must match the set
   in the request, or an error must be returned.
  And if request doesn't contain a body, then it's a GET request.
 
  It means OFPMP_TABLE_FEATURES consists of 2 parts: GET and SET.
  We implement the GET message now, and part of SET.
  But the entire SET message seems difficult, because it configures the
  whole pipeline.
 
  Currently we test the implement via NOX-OF1.3 and testsuite of ovs.
  But some implement (such as the cli) is crude, hope your suggestions. 

 lib/ofp-actions.c          |   16 +
 lib/ofp-actions.h          |    3 +
 lib/ofp-msgs.h             |    4 +-
 lib/ofp-print.c            |  140 +++++++++-
 lib/ofp-util.c             |  699 ++++++++++++++++++++++++++++++++++++++++++++
 lib/ofp-util.h             |  211 +++++++++++++
 lib/rconn.c                |    4 +-
 ofproto/ofproto-provider.h |   14 +
 ofproto/ofproto.c          |  275 +++++++++++++++++-
 tests/ofp-print.at         |  165 +++++++++++
 tests/ofproto.at           |   25 ++
 utilities/ovs-ofctl.c      |   17 +
 12 files changed, 1567 insertions(+), 6 deletions(-)

-- 
1.7.3.1.msysgit.0


_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev

Reply via email to