From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <Waiman.Long@hp.com>
Cc: linux-arch@vger.kernel.org, Rik van Riel <riel@redhat.com>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Scott J Norton <scott.norton@hp.com>,
x86@kernel.org, Paolo Bonzini <paolo.bonzini@gmail.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Ingo Molnar <mingo@redhat.com>, Chegu Vinod <chegu_vinod@hp.com>,
David Vrabel <david.vrabel@citrix.com>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v9 06/19] qspinlock: prolong the stay in the pending bit path
Date: Thu, 17 Apr 2014 18:36:40 +0200 [thread overview]
Message-ID: <20140417163640.GT11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1397747051-15401-7-git-send-email-Waiman.Long@hp.com>
On Thu, Apr 17, 2014 at 11:03:58AM -0400, Waiman Long wrote:
> There is a problem in the current trylock_pending() function. When the
> lock is free, but the pending bit holder hasn't grabbed the lock &
> cleared the pending bit yet, the trylock_pending() function will fail.
I remember seeing some of this..
> It can be seen that the queue spinlock is slower than the ticket
> spinlock when there are 2 or 3 contending tasks. In all the other case,
> the queue spinlock is either equal or faster than the ticket spinlock.
So with my code I get:
qspinlock ticket
local: 2: 8741.853010 2: 8812.042460
remote: 2: 8549.731795 2: 8709.005695
And that is without this optimization.
Also note that I don't have this cmpxchg loop anymore.
> kernel/locking/qspinlock.c | 32 ++++++++++++++++++++++++++++++--
> 1 files changed, 30 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
> index 55601b4..497da24 100644
> --- a/kernel/locking/qspinlock.c
> +++ b/kernel/locking/qspinlock.c
> @@ -216,6 +216,7 @@ xchg_tail(struct qspinlock *lock, u32 tail, u32 *pval)
> static inline int trylock_pending(struct qspinlock *lock, u32 *pval)
> {
> u32 old, new, val = *pval;
> + int retry = 1;
>
> /*
> * trylock || pending
> @@ -225,11 +226,38 @@ static inline int trylock_pending(struct qspinlock *lock, u32 *pval)
> */
> for (;;) {
> /*
> - * If we observe any contention; queue.
> + * If we observe that the queue is not empty,
> + * return and be queued.
> */
> - if (val & ~_Q_LOCKED_MASK)
> + if (val & _Q_TAIL_MASK)
> return 0;
>
> + if ((val & _Q_LOCKED_PENDING_MASK) ==
> + (_Q_LOCKED_VAL|_Q_PENDING_VAL)) {
> + /*
> + * If both the lock and pending bits are set, we wait
> + * a while to see if that either bit will be cleared.
> + * If that is no change, we return and be queued.
> + */
> + if (!retry)
> + return 0;
> + retry--;
> + cpu_relax();
> + cpu_relax();
> + *pval = val = atomic_read(&lock->val);
> + continue;
Since you gave up optimizing the _Q_PENDING_BITS != 8 case why bother
with this? The switch from _Q_PENDING_VAL to _Q_LOCKED_VAL is atomic by
virtue of your (endian challenged) clear_pending_set_locked().
> + } else if ((val & _Q_LOCKED_PENDING_MASK) == _Q_PENDING_VAL) {
> + /*
> + * Pending bit is set, but not the lock bit.
> + * Assuming that the pending bit holder is going to
> + * set the lock bit and clear the pending bit soon,
> + * it is better to wait than to exit at this point.
> + */
> + cpu_relax();
> + *pval = val = atomic_read(&lock->val);
> + continue;
> + }
> +
> new = _Q_LOCKED_VAL;
> if (val == new)
> new |= _Q_PENDING_VAL;
Wouldn't something like:
while (atomic_read(&lock->val) == _Q_PENDING_VAL)
cpu_relax();
before the cmpxchg loop have gotten you all this?
I just tried this on my code and I cannot see a difference.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <Waiman.Long@hp.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-arch@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xenproject.org, kvm@vger.kernel.org,
Paolo Bonzini <paolo.bonzini@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Rik van Riel <riel@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
David Vrabel <david.vrabel@citrix.com>,
Oleg Nesterov <oleg@redhat.com>, Gleb Natapov <gleb@redhat.com>,
Scott J Norton <scott.norton@hp.com>,
Chegu Vinod <chegu_vinod@hp.com>
Subject: Re: [PATCH v9 06/19] qspinlock: prolong the stay in the pending bit path
Date: Thu, 17 Apr 2014 18:36:40 +0200 [thread overview]
Message-ID: <20140417163640.GT11096@twins.programming.kicks-ass.net> (raw)
Message-ID: <20140417163640.1ZJa2CLn26eYaEddfCJKJ8KM5yHmkzaeLnQne8y1yRs@z> (raw)
In-Reply-To: <1397747051-15401-7-git-send-email-Waiman.Long@hp.com>
On Thu, Apr 17, 2014 at 11:03:58AM -0400, Waiman Long wrote:
> There is a problem in the current trylock_pending() function. When the
> lock is free, but the pending bit holder hasn't grabbed the lock &
> cleared the pending bit yet, the trylock_pending() function will fail.
I remember seeing some of this..
> It can be seen that the queue spinlock is slower than the ticket
> spinlock when there are 2 or 3 contending tasks. In all the other case,
> the queue spinlock is either equal or faster than the ticket spinlock.
So with my code I get:
qspinlock ticket
local: 2: 8741.853010 2: 8812.042460
remote: 2: 8549.731795 2: 8709.005695
And that is without this optimization.
Also note that I don't have this cmpxchg loop anymore.
> kernel/locking/qspinlock.c | 32 ++++++++++++++++++++++++++++++--
> 1 files changed, 30 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
> index 55601b4..497da24 100644
> --- a/kernel/locking/qspinlock.c
> +++ b/kernel/locking/qspinlock.c
> @@ -216,6 +216,7 @@ xchg_tail(struct qspinlock *lock, u32 tail, u32 *pval)
> static inline int trylock_pending(struct qspinlock *lock, u32 *pval)
> {
> u32 old, new, val = *pval;
> + int retry = 1;
>
> /*
> * trylock || pending
> @@ -225,11 +226,38 @@ static inline int trylock_pending(struct qspinlock *lock, u32 *pval)
> */
> for (;;) {
> /*
> - * If we observe any contention; queue.
> + * If we observe that the queue is not empty,
> + * return and be queued.
> */
> - if (val & ~_Q_LOCKED_MASK)
> + if (val & _Q_TAIL_MASK)
> return 0;
>
> + if ((val & _Q_LOCKED_PENDING_MASK) ==
> + (_Q_LOCKED_VAL|_Q_PENDING_VAL)) {
> + /*
> + * If both the lock and pending bits are set, we wait
> + * a while to see if that either bit will be cleared.
> + * If that is no change, we return and be queued.
> + */
> + if (!retry)
> + return 0;
> + retry--;
> + cpu_relax();
> + cpu_relax();
> + *pval = val = atomic_read(&lock->val);
> + continue;
Since you gave up optimizing the _Q_PENDING_BITS != 8 case why bother
with this? The switch from _Q_PENDING_VAL to _Q_LOCKED_VAL is atomic by
virtue of your (endian challenged) clear_pending_set_locked().
> + } else if ((val & _Q_LOCKED_PENDING_MASK) == _Q_PENDING_VAL) {
> + /*
> + * Pending bit is set, but not the lock bit.
> + * Assuming that the pending bit holder is going to
> + * set the lock bit and clear the pending bit soon,
> + * it is better to wait than to exit at this point.
> + */
> + cpu_relax();
> + *pval = val = atomic_read(&lock->val);
> + continue;
> + }
> +
> new = _Q_LOCKED_VAL;
> if (val == new)
> new |= _Q_PENDING_VAL;
Wouldn't something like:
while (atomic_read(&lock->val) == _Q_PENDING_VAL)
cpu_relax();
before the cmpxchg loop have gotten you all this?
I just tried this on my code and I cannot see a difference.
next prev parent reply other threads:[~2014-04-17 16:36 UTC|newest]
Thread overview: 131+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 15:03 [PATCH v9 00/19] qspinlock: a 4-byte queue spinlock with PV support Waiman Long
2014-04-17 15:03 ` Waiman Long
2014-04-17 15:03 ` [PATCH v9 01/19] qspinlock: A simple generic 4-byte queue spinlock Waiman Long
2014-04-17 15:03 ` Waiman Long
2014-04-17 15:03 ` [PATCH v9 02/19] qspinlock, x86: Enable x86-64 to use " Waiman Long
2014-04-17 15:03 ` Waiman Long
2014-04-17 15:03 ` [PATCH v9 03/19] qspinlock: Add pending bit Waiman Long
2014-04-17 15:03 ` Waiman Long
2014-04-17 15:42 ` Peter Zijlstra
2014-04-17 15:42 ` Peter Zijlstra
2014-04-17 21:20 ` Waiman Long
2014-04-18 8:13 ` Peter Zijlstra
2014-04-18 8:13 ` Peter Zijlstra
2014-04-18 17:07 ` Waiman Long
2014-04-18 17:07 ` Waiman Long
2014-04-18 7:42 ` Ingo Molnar
2014-04-18 7:42 ` Ingo Molnar
2014-04-18 16:23 ` Waiman Long
2014-04-18 16:23 ` Waiman Long
2014-04-18 16:35 ` Konrad Rzeszutek Wilk
2014-04-18 16:35 ` Konrad Rzeszutek Wilk
2014-04-18 18:12 ` Waiman Long
2014-04-18 18:12 ` Waiman Long
2014-04-17 15:03 ` [PATCH v9 04/19] qspinlock: Extract out the exchange of tail code word Waiman Long
2014-04-17 15:49 ` Peter Zijlstra
2014-04-17 15:49 ` Peter Zijlstra
2014-04-17 21:28 ` Waiman Long
2014-04-17 21:28 ` Waiman Long
2014-04-18 8:15 ` Peter Zijlstra
2014-04-18 8:15 ` Peter Zijlstra
2014-04-18 17:32 ` Waiman Long
2014-04-18 17:32 ` Waiman Long
2014-04-18 17:53 ` Peter Zijlstra
2014-04-18 17:53 ` Peter Zijlstra
2014-04-18 18:13 ` Waiman Long
2014-04-18 18:13 ` Waiman Long
2014-04-17 15:03 ` [PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS Waiman Long
2014-04-17 15:03 ` Waiman Long
2014-04-17 15:50 ` Peter Zijlstra
2014-04-17 15:50 ` Peter Zijlstra
2014-04-17 21:29 ` Waiman Long
2014-04-17 21:29 ` Waiman Long
2014-04-17 15:51 ` Peter Zijlstra
2014-04-17 15:51 ` Peter Zijlstra
2014-04-17 21:33 ` Waiman Long
2014-04-17 21:33 ` Waiman Long
2014-04-17 15:56 ` Peter Zijlstra
2014-04-17 15:56 ` Peter Zijlstra
2014-04-17 21:46 ` Waiman Long
2014-04-17 21:46 ` Waiman Long
2014-04-18 8:27 ` Peter Zijlstra
2014-04-18 8:27 ` Peter Zijlstra
2014-04-18 17:52 ` Waiman Long
2014-04-18 17:52 ` Waiman Long
2014-04-18 19:05 ` Peter Zijlstra
2014-04-18 19:05 ` Peter Zijlstra
2014-04-18 21:40 ` Waiman Long
2014-04-18 21:40 ` Waiman Long
2014-04-23 14:23 ` Waiman Long
2014-04-23 14:23 ` Waiman Long
2014-04-23 14:56 ` Konrad Rzeszutek Wilk
2014-04-23 14:56 ` Konrad Rzeszutek Wilk
2014-04-23 17:43 ` Waiman Long
2014-04-23 17:43 ` Waiman Long
2014-04-23 17:55 ` Konrad Rzeszutek Wilk
2014-04-23 17:55 ` Konrad Rzeszutek Wilk
2014-04-23 22:24 ` Waiman Long
2014-04-23 22:24 ` Waiman Long
2014-04-23 23:48 ` Waiman Long
2014-04-23 23:48 ` Waiman Long
2014-04-17 15:58 ` Peter Zijlstra
2014-04-17 15:58 ` Peter Zijlstra
2014-04-17 21:49 ` Waiman Long
2014-04-17 21:49 ` Waiman Long
2014-04-18 7:46 ` Ingo Molnar
2014-04-18 7:46 ` Ingo Molnar
2014-04-18 16:26 ` Waiman Long
2014-04-18 16:26 ` Waiman Long
2014-04-19 9:24 ` Ingo Molnar
2014-04-19 9:24 ` Ingo Molnar
2014-04-17 15:03 ` [PATCH v9 06/19] qspinlock: prolong the stay in the pending bit path Waiman Long
2014-04-17 15:03 ` Waiman Long
2014-04-17 16:36 ` Peter Zijlstra [this message]
2014-04-17 16:36 ` Peter Zijlstra
2014-04-18 1:46 ` Waiman Long
2014-04-18 1:46 ` Waiman Long
2014-04-18 8:33 ` Peter Zijlstra
2014-04-18 8:33 ` Peter Zijlstra
2014-04-18 18:07 ` Waiman Long
2014-04-18 18:07 ` Waiman Long
2014-04-17 15:03 ` [PATCH v9 07/19] qspinlock: Use a simple write to grab the lock, if applicable Waiman Long
2014-04-17 15:03 ` Waiman Long
2014-04-17 16:54 ` Peter Zijlstra
2014-04-17 16:54 ` Peter Zijlstra
2014-04-17 15:04 ` [PATCH v9 08/19] qspinlock: Make a new qnode structure to support virtualization Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 09/19] qspinlock: Prepare for unfair lock support Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 10/19] qspinlock, x86: Allow unfair spinlock in a virtual guest Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 11/19] qspinlock: Split the MCS queuing code into a separate slowerpath Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 12/19] unfair qspinlock: Variable frequency lock stealing mechanism Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 13/19] unfair qspinlock: Enable lock stealing in lock waiters Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 14/19] pvqspinlock, x86: Rename paravirt_ticketlocks_enabled Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 15/19] pvqspinlock, x86: Add PV data structure & methods Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 16/19] pvqspinlock: Enable coexistence with the unfair lock Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 17/19] pvqspinlock: Add qspinlock para-virtualization support Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 18/19] pvqspinlock, x86: Enable PV qspinlock PV for KVM Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 15:04 ` [PATCH v9 19/19] pvqspinlock, x86: Enable PV qspinlock for XEN Waiman Long
2014-04-17 15:04 ` Waiman Long
2014-04-17 17:23 ` [PATCH v9 00/19] qspinlock: a 4-byte queue spinlock with PV support Konrad Rzeszutek Wilk
2014-04-17 17:23 ` Konrad Rzeszutek Wilk
2014-04-17 17:40 ` Raghavendra K T
2014-04-17 17:40 ` Raghavendra K T
2014-04-18 1:50 ` Waiman Long
2014-04-18 1:48 ` Waiman Long
2014-04-18 1:48 ` Waiman Long
2014-04-18 13:18 ` Konrad Rzeszutek Wilk
2014-04-18 13:18 ` Konrad Rzeszutek Wilk
2014-04-18 17:05 ` Waiman Long
2014-04-18 17:05 ` Waiman Long
2014-04-27 18:09 ` Raghavendra K T
2014-05-07 15:00 ` Waiman Long
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=20140417163640.GT11096@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Waiman.Long@hp.com \
--cc=chegu_vinod@hp.com \
--cc=david.vrabel@citrix.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paolo.bonzini@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).