This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Synchronizing auxiliary mutex data
- From: Andreas Schwab <schwab at suse dot de>
- To: Torvald Riegel <triegel at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Tue, 20 Jun 2017 10:21:13 +0200
- Subject: Re: Synchronizing auxiliary mutex data
- Authentication-results: sourceware.org; auth=none
- References: <mvmtw3cflej.fsf@suse.de> <1497896660.18410.15.camel@redhat.com>
On Jun 19 2017, Torvald Riegel <triegel@redhat.com> wrote:
> * We write to __owner only when in the critical section, with relaxed
> MO; we write TID after lock and 0 before unlock. Those writes are
> ordered by the critical section.
How does it guarantee that the thread calling pthread_mutex_lock see the
change that the thread calling pthread_mutex_unlock did?
> __count is only accessed within the critical section IIRC.
Same here.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."