Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 4 Sep 2002 10:55:30 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: A Simple Real World Benchmark for cygwin Message-ID: <20020904105530.A1213@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Wed, Sep 04, 2002 at 08:34:10AM +0200, Bjoern Kahl AG Resy wrote: > I think, there is a missunderstanding on your side, Corinna > (see below) > [...] > As I understand MSDN, the order of CoInit and CoUnint does not > matter, as long as there is an equal number of CoUninit and CoInit > at Process termination and the (number of CoUninit) <= (number of > CoInit) at every other point of time. > > But then your examples are identical. I do not know details of > the inner cygwin working, so I discuss two possible setups > [...] > Note: it did not matter, if Thread_2 and Thread_X are in > fact the same thread or two different one as shown here. Basically you're argumentation is right except for the different threads. In single-thread apartment mode, which is the only one supported by CoInit, each thread using COM has to call CoInit anyway. However, I think the better way is to change the code to use direct calls to ReadFile and to drop usage of COM. This will eliminate the whole problem and is likely way faster. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/