Acked-by: Eitan Eliahu <[email protected]>

-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Ankur Sharma
Sent: Thursday, October 23, 2014 12:12 PM
To: [email protected]
Subject: [ovs-dev] [PATCH v3 2/3] datapath-windows: Add code for OvsGetQueue.

Signed-off-by: Ankur Sharma <[email protected]>
Acked-by: Sorin Vinturis <[email protected]>
---
 datapath-windows/ovsext/User.c | 21 ++++++++++++++++-----
 1 file changed, 16 insertions(+), 5 deletions(-)

diff --git a/datapath-windows/ovsext/User.c b/datapath-windows/ovsext/User.c 
index 213d606..f6b1157 100644
--- a/datapath-windows/ovsext/User.c
+++ b/datapath-windows/ovsext/User.c
@@ -609,14 +609,25 @@ OvsGetNextPacket(POVS_OPEN_INSTANCE instance)
     return CONTAINING_RECORD(link, OVS_PACKET_QUEUE_ELEM, link);  }
 
-
+/*
+ * 
+-----------------------------------------------------------------------
+----
+ * Given a pid, returns the corresponding USER_PACKET_QUEUE.
+ * gOvsCtrlLock must be acquired before calling this API.
+ * 
+-----------------------------------------------------------------------
+----
+ */
 POVS_USER_PACKET_QUEUE
 OvsGetQueue(UINT32 pid)
 {
-    /* XXX To be implemented. Return the queue assoiated with the pid*/
-    UNREFERENCED_PARAMETER(pid);
-    ASSERT(FALSE);
-    return NULL;
+    POVS_OPEN_INSTANCE instance;
+    POVS_USER_PACKET_QUEUE ret = NULL;
+
+    instance = OvsGetPidInstance(gOvsSwitchContext, pid);
+
+    if (instance) {
+        ret = instance->packetQueue;
+    }
+
+    return ret;
 }
 
 /*
--
1.9.1

_______________________________________________
dev mailing list
[email protected]
https://urldefense.proofpoint.com/v1/url?u=http://openvswitch.org/mailman/listinfo/dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=yTvML8OxA42Jb6ViHe7fUXbvPVOYDPVq87w43doxtlY%3D%0A&m=WgJOac65aJD58EjXss9mRgGKl%2FhP4qYajeVL98RZLpY%3D%0A&s=bb3f862037f3110e2f629b6f88acc9ca85d42701d007831b219ef04eb2c9616e
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev

Reply via email to