mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: [PATCH] Use CAS instead of atomic swap to implement spinlock
Date: Sun, 19 Apr 2015 08:50:18 +0300 (MSK)	[thread overview]
Message-ID: <alpine.LNX.2.11.1504190847320.11963@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20150419002433.GL6817@brightrain.aerifal.cx>

On Sat, 18 Apr 2015, Rich Felker wrote:

> On Wed, Apr 15, 2015 at 01:44:53AM +0300, Alexander Monakov wrote:
> > This should allow spinning without constantly dirtying cache lines holding the
> > spinlock value.  On architectures without native atomic swap, musl implement
> > a_swap by looping around a_cas.
> > ---
> > If I'm not mistaken this was also suggested by nsz on IRC.
> > 
> >  src/thread/pthread_spin_lock.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/src/thread/pthread_spin_lock.c b/src/thread/pthread_spin_lock.c
> > index df575f0..dabcb31 100644
> > --- a/src/thread/pthread_spin_lock.c
> > +++ b/src/thread/pthread_spin_lock.c
> > @@ -2,6 +2,6 @@
> >  
> >  int pthread_spin_lock(pthread_spinlock_t *s)
> >  {
> > -	while (a_swap(s, 1)) a_spin();
> > +	while (a_cas(s, 0, 1)) a_spin();
> >  	return 0;
> >  }
> 
> Would it perhaps be better to do something like this?
> 
> while (*(volatile int *)s || a_cas(s, 0, 1)) a_spin();

I think so, Yes.  Is the cast required, or is it possible to change the
pthread_spinlock_t typedef to 'volatile int'?

Thanks.
Alexander


  reply	other threads:[~2015-04-19  5:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 22:44 Alexander Monakov
2015-04-14 23:16 ` Rich Felker
2015-04-15  6:29   ` Concerns about dlclose() behaviour Brad Conroy
2015-04-15  7:17     ` Rich Felker
2015-04-19  0:24 ` [PATCH] Use CAS instead of atomic swap to implement spinlock Rich Felker
2015-04-19  5:50   ` Alexander Monakov [this message]
2015-04-19  6:01     ` Rich Felker
2015-04-19 12:46       ` Szabolcs Nagy

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=alpine.LNX.2.11.1504190847320.11963@monopod.intra.ispras.ru \
    --to=amonakov@ispras.ru \
    --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).