Hi Guru, Sorry for the delayed response.
Named pipes do not use WSAPoll, nor will it use select. I ran all the unit tests after I switched from WSAPoll to select and all was green. Isolation testing using select rather than WSAPoll show no increase in CPU consumption. Thanks, Alin. From: Guru Shetty [mailto:[email protected]] Sent: Tuesday, December 20, 2016 7:30 PM To: Alin Serdean <[email protected]> Cc: [email protected] Subject: Re: [ovs-dev] [PATCH] windows: WSAPoll broken on windows On 15 December 2016 at 18:50, Alin Serdean <[email protected]<mailto:[email protected]>> wrote: Unfortunately, WSAPoll misbehaves on Windows please view detailed behavior on: https://github.com/openvswitch/ovs-issues/issues/117 We replace the WSAPoll with select looking only for errors and write events. Signed-off-by: Alin Gabriel Serdean <[email protected]<mailto:[email protected]>> Reported-at: https://github.com/openvswitch/ovs-issues/issues/117 Reported-by: Yin Lin <[email protected]<mailto:[email protected]>> Does the select system call in Windows work with named pipes? On that line, did it work with WSAPoll? _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
