; } else {
Regards,
Sam
Date: Thu, 4 Sep 2014 03:18:13 -0700
From: Eitan Eliahu
To: dev@openvswitch.org
Subject: [ovs-dev] [PATCH] Windows NetLink Socket - Support for
asynchronousevent notification
Message-ID: <1409825893-3280-1-git-send-email-elia
} else {
Regards,
Sam
Date: Thu, 4 Sep 2014 03:18:13 -0700
From: Eitan Eliahu
To: dev@openvswitch.org
Subject: [ovs-dev] [PATCH] Windows NetLink Socket - Support for
asynchronousevent notification
Message-ID: <1409825893-3280-1-git-send-email-elia...@vmware.c
tLink Socket - Support for
asynchronous event notification
>We keep an outstanding, out of band, I/O request in the driver at all
>time.
>Once an event generated the driver queues the event message, completes
>the pending I/O and unblocks the calling thread through setting t
>We keep an outstanding, out of band, I/O request in the driver at all
>time.
>Once an event generated the driver queues the event message, completes the
>pending I/O and unblocks the calling thread through setting the event in
>the
>overlapped structure n the NL socket. The thread will read all
Looks good to me.
Acked-by: Ankur Sharma
Regards,
Ankur
From: dev on behalf of Eitan Eliahu
Sent: Thursday, September 4, 2014 3:18 AM
To: dev@openvswitch.org
Subject: [ovs-dev] [PATCH] Windows NetLink Socket - Support for asynchronous
event
We keep an outstanding, out of band, I/O request in the driver at all time.
Once an event generated the driver queues the event message, completes the
pending I/O and unblocks the calling thread through setting the event in the
overlapped structure n the NL socket. The thread will read all all eve
