Re: [PATCH v2 1/3] Posix asynchronous I/O support: aio files

On Apr 19 01:04, Mark Geisert wrote: > This is the core of the AIO implementation: aio.cc and aio.h. The > latter is used within Cygwin by aio.cc and the fhandler* modules, as > well as by user programs wanting the AIO functionality. > > This is the 2nd WIP patch set for AIO. The string XXX mark

Re: [PATCH v2 1/2] Posix asynchronous I/O support: fhandler files

On Apr 19 01:04, Mark Geisert wrote: > This code is where the AIO implementation is wired into existing Cygwin > mechanisms for file and device I/O: the fhandler* functions. It makes > use of an existing internal routine prw_open to supply a "shadow fd" > that permits asynchronous operations on a

Re: [PATCH v2 3/3] Posix asynchronous I/O support: other files

On Apr 19 01:04, Mark Geisert wrote: > Updates to misc files to integrate AIO into the Cygwin source tree. > Much of it has to be done when adding any new syscalls. There are > some updates to limits.h for AIO-specific limits. And some doc mods. > > This is the 2nd WIP patch set for AIO. The st

[PATCH v2 3/3] Posix asynchronous I/O support: other files

Updates to misc files to integrate AIO into the Cygwin source tree. Much of it has to be done when adding any new syscalls. There are some updates to limits.h for AIO-specific limits. And some doc mods. This is the 2nd WIP patch set for AIO. The string XXX marks issues I'm specifically requesti

[PATCH v2 1/3] Posix asynchronous I/O support: aio files

This is the core of the AIO implementation: aio.cc and aio.h. The latter is used within Cygwin by aio.cc and the fhandler* modules, as well as by user programs wanting the AIO functionality. This is the 2nd WIP patch set for AIO. The string XXX marks issues I'm specifically requesting comments o

[PATCH v2 0/3] Posix asynchronous I/O support

This is the 2nd WIP patch set for AIO. The string XXX marks issues I'm specifically requesting comments on, but feel free to comment or suggest changes on any of this code. The code is working for both non-stress and stress situations I can provoke with a test program I have. The code only deals

[PATCH v2 1/2] Posix asynchronous I/O support: fhandler files

This code is where the AIO implementation is wired into existing Cygwin mechanisms for file and device I/O: the fhandler* functions. It makes use of an existing internal routine prw_open to supply a "shadow fd" that permits asynchronous operations on a file the user app accesses via its own fd. T