Acked-by: Ankur Sharma
From: dev on behalf of Eitan Eliahu
Sent: Wednesday, November 12, 2014 10:53 AM
To: Nithin Raju
Cc: dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH 1/7] datapath-windows: fixes in
OvsGetExtInfoIoctl()
Yes, we planned
DISPATCH level IRQL execution before holding the
R/W Dispatch lock.
Besides that It is good.
Thanks,
Eitan
-Original Message-
From: Nithin Raju
Sent: Wednesday, November 12, 2014 10:49 AM
To: Eitan Eliahu
Cc: dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH 1/7] datapath-windows: fixes in
On Nov 12, 2014, at 9:48 AM, Eitan Eliahu 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.
Su
: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Nithin Raju
Sent: Tuesday, November 11, 2014 7:05 PM
To: dev@openvswitch.org
Subject: [ovs-dev] [PATCH 1/7] datapath-windows: fixes in OvsGetExtInfoIoctl()
A few fixes around locking.
Signed-off-by: Nithin Raju
---
datapath-windows/ovsext/Vport.c |
A few fixes around locking.
Signed-off-by: Nithin Raju
---
datapath-windows/ovsext/Vport.c | 16 ++--
1 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/datapath-windows/ovsext/Vport.c b/datapath-windows/ovsext/Vport.c
index a46d49f..ff105b7 100644
--- a/datapath-windo
