From: Greg Smith <gsmith@nc.rr.com>
To: linuxppc-dev@ozlabs.org
Subject: [OT] ppc64 serialization problem
Date: Tue, 28 Mar 2006 20:58:26 -0500 [thread overview]
Message-ID: <1143597506.3075.53.camel@localhost.localdomain> (raw)
We have a multi-threaded app running on a p520 in 64 bit mode.
Thread A does
pthread_mutex_lock(&lock);
u32 &= ~bitA;
pthread_mutex_unlock(&lock);
and Thread B does
pthread_mutex_lock(&lock);
u32 |= bitB;
A = u32;
B = u32;
pthread_mutex_unlock(&lock);
On rare occasions, values A and B will differ! In the examples that I
have seen, there is contention with `lock'. This phenomenon does not
occur on ppc32 or a number of other architectures that we support.
I confess I do not know the linux version nor the glibc version nor what
pthreads implementation is being used. I'll find that out shortly.
What I am curious about is where the problem might lie
(kernel/lib/pthreads/app) so I can ask the right people.
Thank you for your patience,
Greg Smith
next reply other threads:[~2006-03-29 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 1:58 Greg Smith [this message]
2006-03-29 3:11 ` [OT] ppc64 serialization problem Benjamin Herrenschmidt
2006-03-29 4:08 ` Greg Smith
2006-03-29 4:21 ` Benjamin Herrenschmidt
2006-03-29 4:07 ` Paul Mackerras
2006-03-29 18:20 ` Greg Smith
2006-03-29 18:32 ` Olaf Hering
2006-03-29 18:42 ` Ivan Warren
2006-03-29 21:29 ` Ivan Warren
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=1143597506.3075.53.camel@localhost.localdomain \
--to=gsmith@nc.rr.com \
--cc=linuxppc-dev@ozlabs.org \
/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 NNTP newsgroup(s).