On Tue, Feb 02, 2016 at 03:15:12PM -0500, Russell Bryant wrote: > On 02/01/2016 02:12 PM, Ben Pfaff wrote: > > On Mon, Feb 01, 2016 at 10:12:49AM -0500, Russell Bryant wrote: > >> In general, I definitely agree that this problem is something we need to > >> work on. I've been wanting to look into adding a way for users of the > >> IDL API to receive callbacks on row events (create, update, delete) so > >> that it knows which rows it should apply updates for. That's about as > >> far as I've gone though. I haven't written any code yet because I keep > >> staying busy with other things. > > > > That's a necessary feature to implement nlog in ovn-northd. It's there > > now, by the way, contributed by HP. > > Oops ... I remember seeing those patches. I guess I missed them going > in. It seems like we can use those changes to improve things in the > short term without massive disruption to the code base. > > I get the feeling that we may have some parallel work streams here - > some easier optimizations to ovn-northd based on the change tracking > already merged into the IDL API, and then a longer term exploration of > an nlog based ovn-northd. Does that seem reasonable? Assuming that > makes sense, I'd like to start working on using those changes in thge > current ovn-northd.
That's fine, especially if you see low-hanging fruit in ovn-northd. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
