X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 14 Dec 2007 14:52:39 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: VM and non-blocking writes Message-ID: <20071214135239.GJ25863@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <47616D31.7090002@4raccoons.com> <20071213175934.GB25863@calimero.vinschen.de> <476185AF.5000906@4raccoons.com> <20071214111508.GD25863@calimero.vinschen.de> <20071214134147.GG25863@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071214134147.GG25863@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Dec 14 14:41, Corinna Vinschen wrote: > On the other hand, as soon as I call send (or WSASendTo) multiple > times with smaller sizes (I tried with 10k), select starts to > block at one point. But even then strange things happen. After > some time (after 5 seconds, then after 14 seconds, then about every > 60 seconds) select() just signals the socket ready for write and > the next send adds another 10K to the internal buffer. A tcpdump > on the interface shows that no package goes over the line... which > would be a surprise anyway, given that the peer does not even once > call read(). Hmm, a few minutes ago select() mysteriously blocked fully after send has written 19 blocks of 10K each.... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/