On Thu, Jan 22, 2015 at 02:52:32PM +0000, Zoltán Balogh wrote: > Our team is just implementing to add new datapath and the relevant > provider to OVS. The new datapath requires a unique flow identifier to > identify flows all over their life cycles. For identification we > intend to use the sequence number (monitor_seqno) maintained by the > connection manager. This flow id is supposed to be taken from the > rule structure when adding a new flow (rule_insert() API), however > it's value is not set (rule->add_seqno = 0) yet at that moment. > Instead we would like to use the monitor_seqno variable of connection > manager directly to set flow id, but there is no proper get function > available for this. > > We would like to propose a get_monitor_seqno() function to connection > manager for this purpose. Please find below the related calltree.
I think it would be better to just create your own unique number, in the provider's derived rule state, during rule_construct() or rule_insert(), rather than creating what looks like a layering error. _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
