On Mon, Feb 02, 2015 at 08:13:22PM -0800, Shashaankar Reddy wrote:
> I'm working on implementing OFP1.4 specific feature to set/get async
> configuration on a switch.
>
> From the code I understand that OFPTYPE_SET_ASYNC_CONFIG being referred to
> both nicira-xt and OFP13 messages:
> /* OFPRAW_NXT_SET_ASYNC_CONFIG.
> * OFPRAW_OFPT13_SET_ASYNC. */
> The set async config calls from controller gets handled at
> 'handle_openflow__(...)'
>
> Here are my questions:
> # Should I use same OFPTYPE_SET_ASYNC_CONFIG for set config message for
> OFP14, then based on ofpheader->version call another function to decode and
> apply mask settings ?
Yes.
> # Else should I create a new 'OFPTYPE_...' for OFP14, and have altogether a
> different path to make settings ?
No.
> # Also I believe 'enum ofconn_async_msg_type { ...' should be evolved
> with new OFP14 async message types ?
I don't think that OF1.4 introduces any new async message types. If it
does then they should be added there.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
