All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Frysinger <vapier@gentoo.org>, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	uclinux-dist-devel@blackfin.uclinux.org,
	Nick Piggin <npiggin@kernel.dk>
Subject: Re: [PATCH/RFC] asm-generic/mutex-dec.h: add SMP support
Date: Mon, 06 Jun 2011 23:32:58 +0200	[thread overview]
Message-ID: <1307395978.2642.33.camel@edumazet-laptop> (raw)
In-Reply-To: <20110606142301.c0a570da.akpm@linux-foundation.org>

Le lundi 06 juin 2011 à 14:23 -0700, Andrew Morton a écrit :
> On Sun, 29 May 2011 23:19:28 -0400
> Mike Frysinger <vapier@gentoo.org> wrote:
> 
> > To make these guys work on SMP systems, we just need to sprinkle a few
> > barriers around.
> > 
> > Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> > ---
> > note: this is what the Blackfin SMP port is using, but it doesn't seem
> > like other SMP ports are ... so I wonder if we're just trying too hard
> > and these barriers aren't actually necessary ?
> > 
> >  include/asm-generic/mutex-dec.h |    8 +++++++-
> >  1 files changed, 7 insertions(+), 1 deletions(-)
> > 
> > diff --git a/include/asm-generic/mutex-dec.h b/include/asm-generic/mutex-dec.h
> > index f104af7..e746c3c 100644
> > --- a/include/asm-generic/mutex-dec.h
> > +++ b/include/asm-generic/mutex-dec.h
> > @@ -22,6 +22,8 @@ __mutex_fastpath_lock(atomic_t *count, void (*fail_fn)(atomic_t *))
> >  {
> >  	if (unlikely(atomic_dec_return(count) < 0))
> >  		fail_fn(count);

Check Documentation/memory-barriers.txt, around line 1688

atomic_dec_return() implies a full memory barrier on each side of the
operation.

smp_mb() is therefore not needed here


> > +	else
> > +		smp_mb();
> >  }
> >  
> >  /**
> > @@ -39,6 +41,7 @@ __mutex_fastpath_lock_retval(atomic_t *count, int (*fail_fn)(atomic_t *))
> >  {
> >  	if (unlikely(atomic_dec_return(count) < 0))
> >  		return fail_fn(count);
> > +	smp_mb();

atomic_dec_return() implies a full memory barrier.
	smp_mb() is therefore not needed here

> >  	return 0;
> >  }
> >  
> > @@ -58,6 +61,7 @@ __mutex_fastpath_lock_retval(atomic_t *count, int (*fail_fn)(atomic_t *))
> >  static inline void
> >  __mutex_fastpath_unlock(atomic_t *count, void (*fail_fn)(atomic_t *))
> >  {
> > +	smp_mb();

atomic_inc_return() implies a full memory barrier.
	smp_mb() is therefore not needed here


> >  	if (unlikely(atomic_inc_return(count) <= 0))
> >  		fail_fn(count);
> >  }
> > @@ -82,8 +86,10 @@ __mutex_fastpath_unlock(atomic_t *count, void (*fail_fn)(atomic_t *))
> >  static inline int
> >  __mutex_fastpath_trylock(atomic_t *count, int (*fail_fn)(atomic_t *))
> >  {
> > -	if (likely(atomic_cmpxchg(count, 1, 0) == 1))
> > +	if (likely(atomic_cmpxchg(count, 1, 0) == 1)) {
> > +		smp_mb();

atomic_cmpxchg() implies a full memory barrier.
	smp_mb() is therefore not needed here


> >  		return 1;
> > +	}
> >  	return 0;
> >  }
> 
> This patch basically reverts Nick's a8ddac7e53e89cb ("mutex: speed up
> generic mutex implementations").  What's up with that?
> 
> I could try to review this patch but I'm pathetic with barriers.  Help.

Well, I really dont understand this patch, it makes no sense.




      parent reply	other threads:[~2011-06-06 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  3:19 [PATCH/RFC] asm-generic/mutex-dec.h: add SMP support Mike Frysinger
2011-05-30  7:00 ` Arnd Bergmann
2011-06-06 21:23 ` Andrew Morton
2011-06-06 21:31   ` [uclinux-dist-devel] " Mike Frysinger
2011-06-06 22:33     ` Mike Frysinger
2011-06-06 21:32   ` Eric Dumazet [this message]

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=1307395978.2642.33.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.