Dear Sirs,
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.
-> rule_insert()
-x- setting flow id and sending flow data to datapath engine should
happen here
-> complete_operation()
-> ofoperation_complete()
<- ofoperation_complete()
<- complete_operation()
<- rule_insert()
-> ofopgroup_submit()
-> ofopgroup_complete()
-> ofproto_rule_is_hidden()
<- ofproto_rule_is_hidden()
-> ofmonitor_report() -x- set rule->add_seqno
<- ofmonitor_report()
-> ofoperation_destroy()
-> rule_actions_destroy()
<- rule_actions_destroy()
<- ofoperation_destroy()
<- ofopgroup_complete()
<- ofopgroup_submit()
It would be simple to add the function to connmgr that would return the value
of monitor_seqno.
But beside the registration of our provider we would not like to modify the OVS
source code.
So I have following questions regarding this.
- When adding such a getter function to connmgr, could it harm the
normal operation of OVS?
- Is it possible to request adding such a functionality to OVS, so
that the original source code would have that function in connmgr?
Best Regards,
Zoltan Balogh
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
