Hi group, writing software, that bases on OpenFlow 1.3 I found a conceptual issue that keeps me thinking, At this time, it seems that there is no full support for OFPMP_TABLE_FEATURES SET command, while OF1.1,1.2 and 1.3 are enabled in OVS-2.1.2. This is perfectly fine as it is marked optional in the spec.
I do understand that hardware switches can rearrange their TCAMs based on client pipeline models. Due to limited TCAM space, the OFMP_TABLE_FEATURES SET command should ask for the minimum requirements of the model to increase the likelihood of the switch to accept the model. My client code looks like the following: 1 pipeline model exists 2 OFPMP_TABLE_FEATURES GET 3 check for applicability: model -> table features 4 if no: OFPMP_TABLE_FEATURES SET reflecting pipeline model 5. if OFPET_TABLE_FEATURES_FAILED: give up 6. else: continue doing other things A software switch like OVS does not impose any constraints on the table features, so the applicability check will always succeed. However, is there any use for OFPMP_TABLE_FEATURES SET in OVS? Would it help in optimizing DPDK usage? Best regards, Sebastian -- SEBASTIAN SPIES Computer Scientist +49 1577 783 08 83 lnked.in/sspies _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
