> On May 20, 2015, at 11:24 AM, Eitan Eliahu wrote:
> If a NULL sent rather than an overlapped structure, the thread which calls
> DeviceIOControl is blocked until the I/O is completed by the driver.
Agree. So, looks like we don’t need handling for STATUS_PENDING when overlapped
structure is NU
river. It should be fine to block the user mode thread during the WFP
transaction processing.
Thanks,
Eitan
-Original Message-
From: Nithin Raju
Sent: Wednesday, May 20, 2015 11:04 AM
To: Eitan Eliahu; Sorin Vinturis; dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH v2 3/4] netlink: su
Sorin/Eitan,
Do we need this patch or not?
Eitan tells me that if return status is STATUS_PENDING, then the context is
blocked in the kernel. If that is true, we probably don’t need this patch since
control won’t return to userspace at all, till the IRP is complete. This is
especially true sinc
Modified 'nl_sock_transact_multiple__' function to send asynchronous
I/O requests to the kernel driver.
Signed-off-by: Sorin Vinturis
Reported-by: Alin Gabriel Serdean
Reported-at: https://github.com/openvswitch/ovs-issues/issues/64
---
lib/netlink-socket.c | 29 +++--
1
