From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Torvald Riegel <triegel@redhat.com>
Cc: munroesj@us.ibm.com, "Joseph S. Myers" <joseph@codesourcery.com>,
Richard Henderson <rth@twiddle.net>,
libc-ports@sourceware.org, libc-alpha@sourceware.org
Subject: Re: PI mutex support for pthread_cond_* now in nptl
Date: Thu, 21 Feb 2013 04:32:00 -0000 [thread overview]
Message-ID: <20130221043320.GG26842@spoyarek.pnq.redhat.com> (raw)
In-Reply-To: <1361391926.581.1774.camel@triegel.csb>
On Wed, Feb 20, 2013 at 09:25:26PM +0100, Torvald Riegel wrote:
> For example, we've spent quite some time debugging a PI cond var failure
> in the past, and this wasn't made any easier by having several
> (different) versions of the cond var implementation.
I'd like to think that at least the variations are gone now with my
patches, so if you're looking to only do an analysis of the algorithm,
the C code should give sufficient insight into what the
architecture-specific code does.
Siddhesh
next prev parent reply other threads:[~2013-02-21 4:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 10:56 Siddhesh Poyarekar
2013-02-18 23:50 ` Joseph S. Myers
2013-02-19 0:50 ` Joseph S. Myers
2013-02-19 16:42 ` Richard Henderson
2013-02-19 16:49 ` Siddhesh Poyarekar
2013-02-19 17:18 ` Joseph S. Myers
2013-02-19 17:21 ` Siddhesh Poyarekar
2013-02-19 20:06 ` Torvald Riegel
2013-02-20 18:13 ` Steven Munroe
2013-02-20 20:25 ` Torvald Riegel
2013-02-20 22:04 ` Roland McGrath
2013-02-20 22:41 ` Steven Munroe
2013-02-21 4:32 ` Siddhesh Poyarekar [this message]
[not found] ` <1361304381.581.80.camel__6928.53579898856$1361304432$gmane$org@triegel.csb>
2013-02-22 4:11 ` Andi Kleen
[not found] ` <5123AB55.2070100__45742.2411222526$1361292204$gmane$org@twiddle.net>
2013-02-19 17:01 ` Andreas Schwab
2013-02-19 17:18 ` Siddhesh Poyarekar
2013-02-19 17:39 ` Andreas Schwab
2013-02-19 17:52 ` Siddhesh Poyarekar
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=20130221043320.GG26842@spoyarek.pnq.redhat.com \
--to=siddhesh@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=munroesj@us.ibm.com \
--cc=rth@twiddle.net \
--cc=triegel@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).