From: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@redhat.com, dave@stgolabs.net,
will.deacon@arm.com, Waiman.Long@hpe.com,
benh@kernel.crashing.org,
Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Subject: [PATCH] locking/osq: Drop the overload of osq lock
Date: Sat, 25 Jun 2016 13:42:03 -0400 [thread overview]
Message-ID: <1466876523-33437-1-git-send-email-xinhui.pan@linux.vnet.ibm.com> (raw)
An over-committed guest with more vCPUs than pCPUs has a heavy overload
in osq_lock().
This is because vCPU A hold the osq lock and yield out, vCPU B wait
per_cpu node->locked to be set. IOW, vCPU B wait vCPU A to run and
unlock the osq lock. Even there is need_resched(), it did not help on
such scenario.
To fix such bad issue, add a threshold in one while-loop of osq_lock().
The value of threshold is somehow equal to SPIN_THRESHOLD.
perf record -a perf bench sched messaging -g 400 -p && perf report
before patch:
18.09% sched-messaging [kernel.vmlinux] [k] osq_lock
12.28% sched-messaging [kernel.vmlinux] [k] rwsem_spin_on_owner
5.27% sched-messaging [kernel.vmlinux] [k] mutex_unlock
3.89% sched-messaging [kernel.vmlinux] [k] wait_consider_task
3.64% sched-messaging [kernel.vmlinux] [k] _raw_write_lock_irq
3.41% sched-messaging [kernel.vmlinux] [k] mutex_spin_on_owner.is
2.49% sched-messaging [kernel.vmlinux] [k] system_call
after patch:
7.62% sched-messaging [kernel.kallsyms] [k] wait_consider_task
7.30% sched-messaging [kernel.kallsyms] [k] _raw_write_lock_irq
5.93% sched-messaging [kernel.kallsyms] [k] mutex_unlock
5.74% sched-messaging [unknown] [H] 0xc000000000077590
4.37% sched-messaging [kernel.kallsyms] [k] __copy_tofrom_user_powe
2.58% sched-messaging [kernel.kallsyms] [k] system_call
Signed-off-by: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
---
kernel/locking/osq_lock.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/kernel/locking/osq_lock.c b/kernel/locking/osq_lock.c
index 05a3785..922fe5d 100644
--- a/kernel/locking/osq_lock.c
+++ b/kernel/locking/osq_lock.c
@@ -81,12 +81,16 @@ osq_wait_next(struct optimistic_spin_queue *lock,
return next;
}
+/* The threahold should take nearly 0.5ms on most archs */
+#define OSQ_SPIN_THRESHOLD (1 << 15)
+
bool osq_lock(struct optimistic_spin_queue *lock)
{
struct optimistic_spin_node *node = this_cpu_ptr(&osq_node);
struct optimistic_spin_node *prev, *next;
int curr = encode_cpu(smp_processor_id());
int old;
+ int loops;
node->locked = 0;
node->next = NULL;
@@ -118,8 +122,14 @@ bool osq_lock(struct optimistic_spin_queue *lock)
while (!READ_ONCE(node->locked)) {
/*
* If we need to reschedule bail... so we can block.
+ * An over-committed guest with more vCPUs than pCPUs
+ * might fall in this loop and cause a huge overload.
+ * This is because vCPU A(prev) hold the osq lock and yield out,
+ * vCPU B(node) wait ->locked to be set, IOW, wait till
+ * vCPU A run and unlock the osq lock.
+ * NOTE that vCPU A and vCPU B might run on same physical cpu.
*/
- if (need_resched())
+ if (need_resched() || loops++ == OSQ_SPIN_THRESHOLD)
goto unqueue;
cpu_relax_lowlatency();
--
2.4.11
next reply other threads:[~2016-06-25 13:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 17:42 Pan Xinhui [this message]
2016-06-25 14:24 ` [PATCH] locking/osq: Drop the overload of osq lock Peter Zijlstra
2016-06-25 15:21 ` Boqun Feng
2016-06-25 16:09 ` Peter Zijlstra
2016-06-25 16:13 ` Peter Zijlstra
2016-06-25 17:27 ` panxinhui
2016-06-25 19:12 ` Peter Zijlstra
2016-06-26 4:59 ` panxinhui
2016-06-27 7:55 ` Peter Zijlstra
2016-06-27 10:19 ` xinhui
2016-06-25 16:28 ` Boqun Feng
2016-06-25 18:28 ` Peter Zijlstra
2016-06-25 16:15 ` Peter Zijlstra
2016-06-25 16:45 ` Boqun Feng
2016-06-25 17:27 ` panxinhui
2016-06-25 19:20 ` Peter Zijlstra
2016-06-25 19:29 ` Peter Zijlstra
2016-06-26 2:26 ` Boqun Feng
2016-06-26 5:21 ` panxinhui
2016-06-26 6:10 ` Boqun Feng
2016-06-26 6:58 ` panxinhui
2016-06-26 14:11 ` Boqun Feng
2016-06-26 15:54 ` panxinhui
2016-06-26 6:59 ` Boqun Feng
2016-06-26 7:08 ` panxinhui
2016-06-26 14:29 ` Boqun Feng
2016-06-26 15:11 ` panxinhui
2016-06-27 6:45 ` Boqun Feng
2016-06-27 7:36 ` xinhui
2016-06-27 8:09 ` Peter Zijlstra
2016-06-27 10:31 ` Boqun Feng
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=1466876523-33437-1-git-send-email-xinhui.pan@linux.vnet.ibm.com \
--to=xinhui.pan@linux.vnet.ibm.com \
--cc=Waiman.Long@hpe.com \
--cc=benh@kernel.crashing.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.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.
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).