On Thu, Mar 19, 2015 at 12:08:34AM -0700, Andy Zhou wrote: > Currently, each monitor table contains a single hmap 'changes' to > track updates. This patch introduces a new data structure > 'ovsdb_monitor_changes' that stores the updates 'rows' tagged by > its first commit transaction id. Each 'ovsdb_monitor_changes' is > refenece counted allowing multiple jsonrpc_monitors to share them. > > The next patch will allow each ovsdb monitor table to store a list > of 'ovsdb_monitor_changes'. This patch stores only one, same as > before. > > Signed-off-by: Andy Zhou <[email protected]>
Would changes_list be better as an hmap indexed on transaction ID? It would make ovsdb_monitor_table_find_changes() faster. Acked-by: Ben Pfaff <[email protected]> _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
