summaryrefslogtreecommitdiff
path: root/datapath-windows/ovsext/TunnelIntf.h
diff options
context:
space:
mode:
authorSorin Vinturis <svinturis@cloudbasesolutions.com>2015-05-27 16:58:25 +0000
committerBen Pfaff <blp@nicira.com>2015-05-27 12:36:27 -0700
commit5e82ceefd12dfcb954da48d027b47d98dc53676a (patch)
treea13059a1a95de2ffb35b8bd94783cee4338ad484 /datapath-windows/ovsext/TunnelIntf.h
parentb6ec827fe0edb5478ac0f580eaa0597b1166a0fb (diff)
downloadopenvswitch-5e82ceefd12dfcb954da48d027b47d98dc53676a.tar.gz
datapath-windows: Support for custom VXLAN tunnel port
The kernel datapath supports only port 4789 for VXLAN tunnel creation. Added support in order to allow for the VXLAN tunnel port to be configurable to any port number set by the userspace. The patch also checks to see if an existing WFP filter, for the necessary UDP tunnel port, is already created before adding a new one. This is a double check, because currently the userspace also verifies this, but it is necessary to avoid future issues. Custom VXLAN tunnel port requires the addition of a new WFP filter with the new UDP tunnel port. The creation of a new WFP filter is triggered in OvsInitVxlanTunnel function and the removal of the WFP filter in OvsCleanupVxlanTunnel function. But the latter functions are running at IRQL = DISPATCH_LEVEL, due to the NDIS RW lock acquisition, and all WFP calls must be running at IRQL = PASSIVE_LEVEL. This is why I have created a system thread which records all filter addition/removal requests into a list for later processing by the system thread. The ThreadStart routine processes all received requests at IRQL = PASSIVE_LEVEL, which is the required IRQL for the necessary WFP calls for adding/removal of the WFP filters. The WFP filter for the default VXLAN port 4789 is not added anymore at filter attach. All WFP filters for the tunnel ports are added when the tunnel ports are initialized and are removed at cleanup. WFP operation status is then reported to userspace. It is necessary that OvsTunnelFilterUninitialize function is called after OvsClearAllSwitchVports in order to allow for the added WFP filters to be removed. OvsTunnelFilterUninitialize function closes the global engine handle used by most of the WFP calls, including filter removal. Signed-off-by: Sorin Vinturis <svinturis@cloudbasesolutions.com> Reported-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com> Reported-at: https://github.com/openvswitch/ovs-issues/issues/66 Acked-by: Nithin Raju <nithin@vmware.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
Diffstat (limited to 'datapath-windows/ovsext/TunnelIntf.h')
-rw-r--r--datapath-windows/ovsext/TunnelIntf.h15
1 files changed, 15 insertions, 0 deletions
diff --git a/datapath-windows/ovsext/TunnelIntf.h b/datapath-windows/ovsext/TunnelIntf.h
index 82a51459a..6a2c980c5 100644
--- a/datapath-windows/ovsext/TunnelIntf.h
+++ b/datapath-windows/ovsext/TunnelIntf.h
@@ -17,6 +17,10 @@
#ifndef __TUNNEL_INTF_H_
#define __TUNNEL_INTF_H_ 1
+typedef VOID(*PFNTunnelVportPendingOp)(PVOID context,
+ NTSTATUS status,
+ UINT32 *replyLen);
+
/* Tunnel callout driver load/unload functions */
NTSTATUS OvsInitTunnelFilter(PDRIVER_OBJECT driverObject, PVOID deviceObject);
@@ -26,4 +30,15 @@ VOID OvsRegisterSystemProvider(PVOID deviceObject);
VOID OvsUnregisterSystemProvider();
+NTSTATUS OvsTunelFilterCreate(PIRP irp,
+ UINT16 filterPort,
+ UINT64 *filterID,
+ PFNTunnelVportPendingOp callback,
+ PVOID context);
+
+NTSTATUS OvsTunelFilterDelete(PIRP irp,
+ UINT64 filterID,
+ PFNTunnelVportPendingOp callback,
+ PVOID context);
+
#endif /* __TUNNEL_INTF_H_ */