This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7.8: write fails with EAGAIN
- From: Brian Ford <Brian dot Ford at FlightSafety dot com>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 7 Mar 2011 13:09:40 -0600
- Subject: Re: 1.7.8: write fails with EAGAIN
- References: <4D72992D.email@example.com> <20110307103951.GL6393@calimero.vinschen.de> <20110307153708.GA2538@ednor.casa.cgf.cx> <20110307163849.GA26824@ednor.casa.cgf.cx> <20110307171045.GA26028@ednor.casa.cgf.cx>
- Reply-to: cygwin-developers at cygwin dot com
On Mon, 7 Mar 2011, Christopher Faylor wrote:
> So, my options are to:
> 1) Limit the buffer size to some value like 64 mib and expect the caller to
> deal with that.
> 2) Limit the buffer size to some value like 64 mib and loop in
> fhandler_overlapped::write_overlapped until everything has been written.
> 3) Attempt the WriteFile(), notice the error condition and then do 1) or 2).
> Just thinking out loud here. I think I've convinced myself that I should
> go with 3 + 2.
I'm not sure I understand what 3 + 2 means here, but in general, on
Windows, overlapped I/O should always be limited to 16 Mb I/Os to avoid
these types of resource issues as described here:
> max < 16M to avoid resource issues
Staff Realtime Software Engineer
VITAL - Visual Simulation Systems
the best safety device in any aircraft is a well-trained crew...