diff options
Diffstat (limited to 'datapath-windows/ovsext/Datapath.h')
| -rw-r--r-- | datapath-windows/ovsext/Datapath.h | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/datapath-windows/ovsext/Datapath.h b/datapath-windows/ovsext/Datapath.h index dbc9dea58..2c61d8217 100644 --- a/datapath-windows/ovsext/Datapath.h +++ b/datapath-windows/ovsext/Datapath.h @@ -52,20 +52,6 @@ typedef struct _OVS_OPEN_INSTANCE { POVS_USER_PACKET_QUEUE packetQueue; UINT32 pid; - /* - * On platforms that support netlink natively, there's generally some form of - * serialization between concurrent calls to netlink sockets. However, OVS - * userspace guarantees that a given netlink handle is not concurrently used. - * Despite this, we do want to have some basic checks in the kernel to make - * sure that things don't break if there are concurrent calls. - * - * This is generally not an issue since kernel data structure access should - * be sychronized anyway. Only reason to have this safeguared is to protect - * the state in "state-aware" read calls which rely on previous state. This - * restriction might go away as the userspace code gets implemented. - */ - INT inUse; - struct { POVS_MESSAGE ovsMsg; /* OVS message passed during dump start. */ UINT32 index[2]; /* markers to continue dump from. One or more |