This is the mail archive of the cygwin-patches mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Nov 29 13:04, Corinna Vinschen wrote: > - If you do async IO, you have to handle STATUS_PENDING gracefully: > > - The IO_STATUS_BLOCK given to NtWriteFile *must* exist for the > entire time the operation takes after NtWriteFile returned > STATUS_PENDING. An IO_STATUS_BLOCK fhandler member comes to mind, > maybe fhandler_base_overlapped::io_status can be reused. No, wait. There can be more than one outstanding aio operations on the same descriptor. Therefore the IO_STATUS_BLOCK must be connected to the aiocb struct one way or the other, becasue only that struct is local to the aio operation. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Attachment:
signature.asc
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |