On Thu, 30 Nov 2017, Corinna Vinschen wrote:
On Nov 30 01:50, Mark Geisert wrote:
Yes, I believe that's correct. But in my aio implementation for Cygwin, I'm
not using overlapped I/O or any kind of async or nonblocking write. I'm
using separate threads to do plain vanilla blocking writes (via p
On Dec 1 00:44, Mark Geisert wrote:
> On Thu, 30 Nov 2017, Corinna Vinschen wrote:
> > On Nov 30 01:50, Mark Geisert wrote:
> > > Yes, I believe that's correct. But in my aio implementation for Cygwin,
> > > I'm
> > > not using overlapped I/O or any kind of async or nonblocking write. I'm
> > >
On Dec 1 10:30, Corinna Vinschen wrote:
> On Dec 1 00:44, Mark Geisert wrote:
> > [...]
> > I'd better take this info back to "the lab" and do some more digging. Thanks
> > very much for these details and your earlier replies. When I saw
> > FILE_SYNCHRONOUS_IO_NONALERT in your reply, I remember
On Fri, 1 Dec 2017, Corinna Vinschen wrote:
On Dec 1 10:30, Corinna Vinschen wrote:
On Dec 1 00:44, Mark Geisert wrote:
[...]
I'd better take this info back to "the lab" and do some more digging. Thanks
very much for these details and your earlier replies. When I saw
FILE_SYNCHRONOUS_IO_NONA
