public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: A Simple Real World Benchmark for cygwin
Date: Wed, 04 Sep 2002 01:55:00 -0000	[thread overview]
Message-ID: <20020904105530.A1213@cygbert.vinschen.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0209040749130.1042-100000@domino.informatik.uni-kl.de>

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@cygwin.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/

  reply	other threads:[~2002-09-04  8:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  8:20 A Simple Real World Benchmark for Cygwin Rick Richardson
2002-09-02  8:36 ` Ville Herva
2002-09-02  8:55 ` A Simple Real World Benchmark for cygwin Christopher Faylor
2002-09-02 14:34   ` Dan Vasaru
2002-09-02 15:02     ` Christopher Faylor
2002-09-03  1:28       ` Corinna Vinschen
2002-09-03  2:38         ` dvasaru
2002-09-03  4:52           ` Corinna Vinschen
2002-09-03  4:59             ` Robert Collins
2002-09-03  5:42               ` Corinna Vinschen
2002-09-03  9:05                 ` Dan Vasaru
2002-09-03 23:34                   ` Bjoern Kahl AG Resy
2002-09-04  1:55                     ` Corinna Vinschen [this message]
2002-09-04  2:10                       ` Bjoern Kahl AG Resy
2002-09-04  2:22                         ` Corinna Vinschen
2002-09-04 14:44                           ` BASH slow on network share scripts (was RE: A Simple Real World Benchmark for cygwin) Dan Vasaru
2002-09-04 20:07                             ` Christopher Faylor
2002-09-02  9:06 ` A Simple Real World Benchmark for Cygwin Michael Hoffman
2002-09-02 11:37   ` Randall R Schulz
2002-09-02 21:31   ` Jeremy Hetzler
2002-09-03 10:58 ` Eric M. Monsler
2002-09-04 10:54   ` Shankar Unni
2002-09-05 17:50 ` Randall R Schulz
2002-09-02  9:51 John Vincent
2002-09-02 10:36 ` Nicholas Wourms
2002-09-03  9:08 A Simple Real World Benchmark for cygwin Robb, Sam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020904105530.A1213@cygbert.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).