Date: Fri, 14 Mar 2008 12:47:13 +0100
From: Mojmir Svoboda <mojmir.svoboda@illusionsoftworks.com>
To: cygwin@cygwin.com
Subject: Re: Re: pthread_mutex_lock/unlock performance?
Message-ID: <20080314114713.GA2730@msvoboda>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080313093028.GA31841@calimero.vinschen.de>
User-Agent: Mutt/1.5.14 (2007-02-12)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

morning, Corinna

> > the thing is that cygwin's pthread_mutex_lock performs quite lazily it
> > takes about seven times more than using native critical section.

> Bookkeeping overhead? 

excuse my unfamiliarity with the matter, but i have no exact idea what
bookkeping could be. could you elaborate the answer more, please?
or point me to some article/documentation where i can read more?

> Just have a look into the Cygwin source.

yes, that's first place i tried to look, but got little disoriented
with the _ and __ versions of the pthread_mutex_lock. i've eventually
finished in __pthread_lock. am i on the right track?

> If you want to speed up Cygwin's pthread implementation, feel free to
> contribute:  http://cygwin.com/contrib.html

well i'm using windows and cygwin for few months so i quite don't feel 
ready... yet ;)

best regards,
Mojmir

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