On Nov 12, 2014, at 9:48 AM, Eitan Eliahu <elia...@vmware.com> wrote:
> I don't see a reason why this function need to be called with gOvsCtrlLock > held. The contention is on the Hyper-V VSwitch port when a port could be > removed from a different thread context. But, this is taken care of by > dispatch lock. Sure, I plan to address the role for 'gOvsCtrlLock' in one sweep in the near future (as you know). Thanks for your input. I'll keep that in mind. Until then, I don't want to let be the usages of 'gOvsCtrlLock'. Do the rest of the changes look ok? Thanks, -- Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
