On Wed, Oct 28, 2015 at 05:45:17AM +0000, Ansari, Shad wrote: > Ovsdb-idl notifies a client that something changed; it does not track > > which table, row changed in what way (insert, modify or delete). > > As a result, a client has to scan or reconfigure the entire idl after > > ovsdb_idl_run(). This is presumably fine for typical ovs schemas where > > tables are relatively small. In use-cases where ovsdb is used with > > schemas that can have very large tables, the current ovsdb-idl > > notification mechanism does not appear to scale - clients need to do a > > lot of processing to determine the exact change delta.
Applied to master, thanks! _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
