From: Gao Xiang <hsiangkao@aol.com>
To: Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Miao Xie <miaoxie@huawei.com>,
Chao Yu <chao@kernel.org>, Gao Xiang <hsiangkao@aol.com>
Subject: [RFC PATCH] bit_spinlock: introduce smp_cond_load_relaxed
Date: Sat, 13 Oct 2018 14:47:29 +0800 [thread overview]
Message-ID: <1539413249-4402-1-git-send-email-hsiangkao@aol.com> (raw)
It is better to use smp_cond_load_relaxed instead
of busy waiting for bit_spinlock.
Signed-off-by: Gao Xiang <hsiangkao@aol.com>
---
include/linux/bit_spinlock.h | 21 ++++++++-------------
1 file changed, 8 insertions(+), 13 deletions(-)
diff --git a/include/linux/bit_spinlock.h b/include/linux/bit_spinlock.h
index bbc4730..713efc4 100644
--- a/include/linux/bit_spinlock.h
+++ b/include/linux/bit_spinlock.h
@@ -15,22 +15,17 @@
*/
static inline void bit_spin_lock(int bitnum, unsigned long *addr)
{
- /*
- * Assuming the lock is uncontended, this never enters
- * the body of the outer loop. If it is contended, then
- * within the inner loop a non-atomic test is used to
- * busywait with less bus contention for a good time to
- * attempt to acquire the lock bit.
- */
- preempt_disable();
#if defined(CONFIG_SMP) || defined(CONFIG_DEBUG_SPINLOCK)
- while (unlikely(test_and_set_bit_lock(bitnum, addr))) {
- preempt_enable();
- do {
- cpu_relax();
- } while (test_bit(bitnum, addr));
+ while (1) {
+ smp_cond_load_relaxed(&addr[BIT_WORD(bitnum)],
+ !(VAL >> (bitnum & (BITS_PER_LONG-1))));
preempt_disable();
+ if (!test_and_set_bit_lock(bitnum, addr))
+ break;
+ preempt_enable();
}
+#else
+ preempt_disable();
#endif
__acquire(bitlock);
}
--
2.7.4
next reply other threads:[~2018-10-13 6:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 6:47 Gao Xiang [this message]
2018-10-13 7:04 ` [RFC PATCH] bit_spinlock: introduce smp_cond_load_relaxed Greg Kroah-Hartman
2018-10-13 7:22 ` Gao Xiang
2018-10-13 7:30 ` Greg Kroah-Hartman
2018-10-13 7:44 ` Gao Xiang
2018-10-13 7:30 ` Gao Xiang
2018-10-30 6:04 ` [PATCH v2] " Gao Xiang
2018-10-30 5:52 ` Gao Xiang
2018-11-05 17:11 ` Gao Xiang
2018-11-05 22:49 ` Will Deacon
2018-11-06 1:45 ` Gao Xiang
2018-11-06 9:06 ` Peter Zijlstra
2018-11-06 10:22 ` Gao Xiang
2018-11-06 11:00 ` Peter Zijlstra
2018-11-06 11:36 ` Gao Xiang
2018-11-06 12:27 ` Peter Zijlstra
2018-11-06 12:33 ` Gao Xiang
2018-11-06 12:38 ` Gao Xiang
2018-11-06 12:43 ` Peter Zijlstra
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=1539413249-4402-1-git-send-email-hsiangkao@aol.com \
--to=hsiangkao@aol.com \
--cc=chao@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
/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