X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-AntiVirus: scanned for viruses by soLNet AVirCheck 2.0.53 (http://www.solnet.cz/avircheck) Date: Fri, 14 Mar 2008 12:47:13 +0100 From: Mojmir Svoboda To: cygwin AT cygwin DOT 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> X-Operating-System: Linux 2.6.20-2925.9.fc7xen X-ICQ-UIN: 37571205 User-Agent: Mutt/1.5.14 (2007-02-12) 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 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/