From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pthreads-win32-return-983-listarch-pthreads-win32=sources.redhat.com@sources.redhat.com>
Received: (qmail 2986 invoked by alias); 12 Apr 2005 10:10:46 -0000
Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:pthreads-win32-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/pthreads-win32/>
List-Post: <mailto:pthreads-win32@sources.redhat.com>
List-Help: <mailto:pthreads-win32-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: pthreads-win32-owner@sources.redhat.com
Received: (qmail 2816 invoked from network); 12 Apr 2005 10:10:35 -0000
Received: from unknown (HELO mtagate4.de.ibm.com) (195.212.29.153)
  by sourceware.org with SMTP; 12 Apr 2005 10:10:35 -0000
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate4.de.ibm.com (8.12.10/8.12.10) with ESMTP id j3CAAXWM130884
	for <pthreads-win32@sources.redhat.com>; Tue, 12 Apr 2005 10:10:33 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228])
	by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id j3CAAXxU202304
	for <pthreads-win32@sources.redhat.com>; Tue, 12 Apr 2005 12:10:33 +0200
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j3CAAXCs029077
	for <pthreads-win32@sources.redhat.com>; Tue, 12 Apr 2005 12:10:33 +0200
Received: from d12ml062.megacenter.de.ibm.com (d12ml062.megacenter.de.ibm.com [9.149.166.219])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j3CAAWrK029066;
	Tue, 12 Apr 2005 12:10:32 +0200
In-Reply-To: <1113291983.23876.44.camel@desk.home>
Subject: Re: New pthreads-w32 releases available: versions 2.3.0 and 1.7.0
To: Ross Johnson <RossJohnson@homemail.com.au>
Cc: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Message-ID: <OF71257A66.8271DD9E-ONC1256FE1.0036A008-C1256FE1.0037C3E4@de.ibm.com>
From: Alexander Terekhov <TEREKHOV@de.ibm.com>
Date: Tue, 12 Apr 2005 10:10:00 -0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-SW-Source: 2005/txt/msg00065.txt.bz2


[... pthread_once() ...]

I'm not inclined to check the code at the moment, but I can tell
you that robust approach to priority problems is to use locks with
priority protocols on the them. Trying to optimize-out mutex
doesn't make much sense here since you need it on slow path (once
per thread per once_control instance at most) only.

Variation of DCSI (either MBR or TLS) with named mutex is the way
to go.

regards,
alexander.