From: Alexander Terekhov <TEREKHOV@de.ibm.com>
To: Ross Johnson <RossJohnson@homemail.com.au>
Cc: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Subject: Re: New pthreads-w32 releases available: versions 2.3.0 and 1.7.0
Date: Tue, 12 Apr 2005 10:10:00 -0000 [thread overview]
Message-ID: <OF71257A66.8271DD9E-ONC1256FE1.0036A008-C1256FE1.0037C3E4@de.ibm.com> (raw)
In-Reply-To: <1113291983.23876.44.camel@desk.home>
[... 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.
next prev parent reply other threads:[~2005-04-12 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 7:46 Ross Johnson
2005-04-12 10:10 ` Alexander Terekhov [this message]
2005-04-13 7:45 ` Ross Johnson
2005-04-13 8:21 ` Gottlob Frege
2005-04-14 16:19 ` Alexander Terekhov
2005-04-15 3:08 ` Ross Johnson
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=OF71257A66.8271DD9E-ONC1256FE1.0036A008-C1256FE1.0037C3E4@de.ibm.com \
--to=terekhov@de.ibm.com \
--cc=RossJohnson@homemail.com.au \
--cc=pthreads-win32@sources.redhat.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).