Date: Tue, 16 Oct 2012 10:38:48 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: signalfd support
Message-ID: <20121016143848.GA25807@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <7503790 DOT 99DVW17TaN AT bob-kubuntu> <507D534B DOT 5040803 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <507D534B.5040803@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Oct 16, 2012 at 02:30:03PM +0200, Noel Grandin wrote:
>
>On 2012-10-16 14:22, bob wrote:
>> In a previous posting a few weeks back I presented some test code which
>> illustrated the performance deficit in the current Cygwin fifo implementation (2
>> orders of magnitude slower than Linux on same hardware).      It was this
>> performance issue that led me on a search for an alternative synchronization
>>
>
>Rather than jumping through hoops to get Cygwin to work, why don't you 
>just use one the built-in native facilities on windows?
>Windows natively supports message queues, asynchronous IO and probably a 
>whole host of other stuff that I don't know about.
>
>You can even access the native Windows functionality while running the 
>rest of your app under cygwin.

Mixing Windows and Cygwin APIs is rarely a good idea.  Some programs, like
mintty, need to do it for obvious reasons but mixing Windows handles and
Cygwin fds is going to cause headaches.

cgf

--
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