: Monday, 13 April, 2015 18:52
To: Sorin Vinturis
Cc: dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH] datapath-windows: Removed gOvsCtrlLock global
spinlock
Sorin,
In general, ‘gOvsControlLock’ is there to protect ‘gOvsSwitchContext’.
Basically, while we are accessing ‘gOvsSwitchContext’ from the
Sorin,
In general, ‘gOvsControlLock’ is there to protect ‘gOvsSwitchContext’.
Basically, while we are accessing ‘gOvsSwitchContext’ from the netlink path or
even during an NDIS switch callback, we want to make sure ‘gOvsSwitchContext’
doesn’t get deallocated under the rug in another context.
Al
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.
Signed-off-by: Sorin Vinturis
---
da
