mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/rtmutex: remove unused cmpxchg_relaxed
Date: Wed, 12 Feb 2020 07:07:56 -0800	[thread overview]
Message-ID: <20200212150756.vmehbn3znt6tnp3t@linux-p48b> (raw)
In-Reply-To: <87c1cdbc-6af0-3f56-e986-b9df894fe4da@linux.alibaba.com>

On Tue, 04 Feb 2020, Alex Shi wrote:

>Thanks Thomas and David!
>Is this following patch ok?

So if anything, this really wants to be two patches.

>---
>From 4cf9e38a73c67c6894f3addb2ddca26bb51b1a28 Mon Sep 17 00:00:00 2001
>From: Alex Shi <alex.shi@linux.alibaba.com>
>Date: Tue, 21 Jan 2020 15:03:33 +0800
>Subject: [PATCH v2] locking/rtmutex: optimize rt_mutex_cmpxchg_xxx series func
>
>rt_mutex_cmpxchg_relexed isn't interested by anyone, so remove it.
>And Davidlohr Bueso suggests check l->owner before cmpxchg to reduce
>lock contention.
>
>Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
>Cc: Thomas Gleixner <tglx@linutronix.de>
>Cc: Davidlohr Bueso <dave@stgolabs.net>
>Cc: Ingo Molnar <mingo@redhat.com>
>Cc: Will Deacon <will@kernel.org>
>Cc: linux-kernel@vger.kernel.org
>---
> kernel/locking/rtmutex.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
>diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
>index 851bbb10819d..eb26f4e57ce4 100644
>--- a/kernel/locking/rtmutex.c
>+++ b/kernel/locking/rtmutex.c
>@@ -141,9 +141,10 @@ static void fixup_rt_mutex_waiters(struct rt_mutex *lock)
>  * set up.
>  */
> #ifndef CONFIG_DEBUG_RT_MUTEXES
>-# define rt_mutex_cmpxchg_relaxed(l,c,n) (cmpxchg_relaxed(&l->owner, c, n) == c)
>-# define rt_mutex_cmpxchg_acquire(l,c,n) (cmpxchg_acquire(&l->owner, c, n) == c)
>-# define rt_mutex_cmpxchg_release(l,c,n) (cmpxchg_release(&l->owner, c, n) == c)
>+# define rt_mutex_cmpxchg_acquire(l,c,n)	\
>+		(l->owner == c && cmpxchg_acquire(&l->owner, c, n) == c)
>+# define rt_mutex_cmpxchg_release(l,c,n)	\
>+		(l->owner == c && cmpxchg_release(&l->owner, c, n) == c)

Thomas, should I resend the top-waiter spin series? Otherwise yeah,
I see little point to the CCAS fastpath thing.

Thanks,
Davidlohr

  reply	other threads:[~2020-02-12 15:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21  8:34 Alex Shi
2020-01-31 17:39 ` Davidlohr Bueso
2020-01-31 20:23   ` Thomas Gleixner
2020-02-04 10:18     ` Alex Shi
2020-02-12 15:07       ` Davidlohr Bueso [this message]
2020-02-14 15:17       ` [PATCH 1/2] locking/rtmutex: Remove unused rt_mutex_cmpxchg_relaxed() Alex Shi
2020-02-14 15:17         ` [PATCH 2/2] locking/rtmutex: optimize rt_mutex_cmpxchgs Alex Shi

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=20200212150756.vmehbn3znt6tnp3t@linux-p48b \
    --to=dave@stgolabs.net \
    --cc=alex.shi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®