On Thu, Apr 23, 2015 at 08:46:40AM +, Sorin Vinturis wrote:
> There is no need to use gOvsCtrlLock spinlock to guard the switch
> context, as there is now the switch context's reference count used
> for this purpose.
>
> Now the gOvsCtrlLock spinlock guards only one shared resource, the
> OVS_
There is no need to use gOvsCtrlLock spinlock to guard the switch
context, as there is now the switch context's reference count used
for this purpose.
Now the gOvsCtrlLock spinlock guards only one shared resource, the
OVS_OPEN_INSTANCE global instance array.
v2: Atomically test and set if the ins
