From: "Václav Haisman" <vhaisman@gmail.com>
To: cygwin-patches@cygwin.com
Subject: Fwd: [PATCH] spinlock spin with pause instruction
Date: Fri, 11 Mar 2016 10:28:00 -0000 [thread overview]
Message-ID: <CAKw7uVg78t2V8KKLYfPyhb97XjU+aUb4KV-poz7i_wwDeJ6b=g@mail.gmail.com> (raw)
In-Reply-To: <CAKw7uVgrjqZVznRMoCbsjyz4YXast5YtAAmpWQorOw7YXqbOhw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
Hi.
I have noticed that Cygwin's spinlock goes into heavy sleeping code
for each spin. It seems it would be a good idea to actually try to
spin a bit first. There is this 'pause' instruction which let's the
CPU make such busy loops be less busy. Here is a patch to do this.
--
VH
[-- Attachment #2: spinlock-pause.patch.txt --]
[-- Type: text/plain, Size: 1258 bytes --]
diff --git a/winsup/cygwin/thread.cc b/winsup/cygwin/thread.cc
index 01cfd5b..56e66f1 100644
--- a/winsup/cygwin/thread.cc
+++ b/winsup/cygwin/thread.cc
@@ -1917,6 +1917,19 @@ pthread_spinlock::lock ()
{
pthread_t self = ::pthread_self ();
int result = -1;
+ unsigned spins = 0;
+
+ /*
+ We want to spin using 'pause' instruction on multi-core system but we
+ want to avoid this on single-core systems.
+
+ The limit of 1000 spins is semi-arbitrary. Microsoft suggests (in their
+ InitializeCriticalSectionAndSpinCount documentation on MSDN) they are
+ using spin count limit 4000 for their heap manager critical
+ sections. Other source suggest spin count as small as 200 for fast path
+ of mutex locking.
+ */
+ unsigned const FAST_SPINS_LIMIT = wincap.cpu_count () != 1 ? 1000 : 0;
do
{
@@ -1925,8 +1938,13 @@ pthread_spinlock::lock ()
set_owner (self);
result = 0;
}
- else if (pthread::equal (owner, self))
+ else if (unlikely(pthread::equal (owner, self)))
result = EDEADLK;
+ else if (spins < FAST_SPINS_LIMIT)
+ {
+ ++spins;
+ __asm__ volatile ("pause":::);
+ }
else
{
/* Minimal timeout to minimize CPU usage while still spinning. */
next parent reply other threads:[~2016-03-11 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKw7uVgrjqZVznRMoCbsjyz4YXast5YtAAmpWQorOw7YXqbOhw@mail.gmail.com>
2016-03-11 10:28 ` Václav Haisman [this message]
2016-03-11 13:04 ` Corinna Vinschen
2016-03-12 6:25 ` Fwd: " Mark Geisert
2016-03-12 8:14 ` Václav Haisman
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='CAKw7uVg78t2V8KKLYfPyhb97XjU+aUb4KV-poz7i_wwDeJ6b=g@mail.gmail.com' \
--to=vhaisman@gmail.com \
--cc=cygwin-patches@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).