From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: What's left for 1.1.11 release?
Date: Tue, 28 Jul 2015 10:18:03 -0400 [thread overview]
Message-ID: <20150728141803.GS16376@brightrain.aerifal.cx> (raw)
In-Reply-To: <1438092578.19958.4.camel@inria.fr>
On Tue, Jul 28, 2015 at 04:09:38PM +0200, Jens Gustedt wrote:
> Hello,
>
> Am Montag, den 27.07.2015, 23:40 -0400 schrieb Rich Felker:
> > In principle the a_store issue affects all libc-internal __lock/LOCK
> > uses,
>
> so this worries me since I assumed that UNLOCK had release consistency
> for the __atomic implementation.
It does. The problem is that it lacks acquire consistency, which we
need in order to know whether to wake.
> > and stdio locks too, but it's only been observed in malloc.
> > Since there don't seem to be any performance-relevant uses of a_store
> > that don't actually need the proper barrier, I think we have to just
> > put an explicit barrier (lock orl $0,(%esp) or mfence) after the store
> > and live with the loss of performance.
>
> How about using a xchg as instruction? This would perhaps "waste" a
> register, but that sort of optimization should not be critical in the
> vicinity of code that needs memory synchronization, anyhow.
How is this better? My intent was to avoid incurring a read on the
cache line that's being written and instead achieve the
synchronization by poking at a cache line (the stack) that should not
be shared.
Rich
next prev parent reply other threads:[~2015-07-28 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 3:40 Rich Felker
2015-07-28 14:09 ` Jens Gustedt
2015-07-28 14:18 ` Rich Felker [this message]
2015-07-28 14:50 ` Jens Gustedt
2015-07-28 14:58 ` Rich Felker
2015-07-28 15:15 ` Jens Gustedt
2015-07-28 16:07 ` Rich Felker
2015-07-28 16:42 ` Jens Gustedt
2015-07-28 17:33 ` Rich Felker
2015-07-28 14:33 ` Alexander Monakov
2015-07-28 17:31 ` Rich Felker
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=20150728141803.GS16376@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).