On Wed, Oct 08, 2014 at 03:19:29PM -0700, Alex Wang wrote: > When ovs-vswitchd fails to acquire the ovsdb idl lock (either due to > contention or due to invalid database path), ovs-vswitchd will spin > on the global connectivity sequence number and consume 100% cpu. > This is in that the local copy is different to the global sequence > number and never updated when ovsdb idl is not locked. > > To fix this issue, this commit makes ovs-vswitchd not checking the > global connectivity sequence number in that situation. > > Signed-off-by: Alex Wang <[email protected]>
Do we need the new variable? Can we just call ovsdb_idl_has_lock() from status_update_wait? _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
