X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.4 required=5.0 tests=AWL,BAYES_50,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Date: Mon, 30 Aug 2010 12:49:01 -0500 From: Brian Ford To: cygwin AT cygwin DOT com Subject: Re: /dev/windows and select() [was Re: Slow response to keypresses in xorg-server-1.8.0-1] In-Reply-To: <20100830112313.GN6726@calimero.vinschen.de> Message-ID: References: <20100830112313 DOT GN6726 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, 30 Aug 2010, Corinna Vinschen wrote: > I applied a patch to Cygwin which should make select on /dev/windows > fully functional. > > The blessed solution is to replace the call to MsgWaitForMultipleObjects > with a call to MsgWaitForMultipleObjectsEx with the MWMO_INPUTAVAILABLE > flag set. This flag is defined to do exactly what we need. Just wondering, does this also effect select/poll on sockets in either 1.7 or 1.5? I seem to remember a Windows event loop required for select on sockets and wasn't sure if this change would be related. A long time ago (1.5.18) I discovered a delay in select on sockets and wondered if this might have been related. I haven't retested in that long since I found a work-around ;-). -- Brian Ford Staff Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple