From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: bisected: futex regression >= 3.14 - was - Slowdown due to threads bouncing between HT cores
Date: Wed, 8 Oct 2014 18:45:57 +0200 [thread overview]
Message-ID: <20141008164557.GB38790@sesse.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1410081756250.4292@nanos>
On Wed, Oct 08, 2014 at 06:14:18PM +0200, Thomas Gleixner wrote:
> It looks far more like an issue with the stocking fish code, but hell
> with futexes one can never be sure.
OK, maybe we should move to a more recent Stockfish version first of all;
the specific benchmark was about that specific binary, but for tracking down
futex issues we can see if more recent code fixes it (the SMP in this thing
keeps getting developed).
I'm moving to 2ac206e847a04a7de07690dd575c6949e5625115 (current head) of
https://github.com/mcostalba/Stockfish.git, and building with
“make -j ARCH=x86-64-bmi2”.
I still don't see any hangs, but I do see the same behavior of moving around
between CPUs as the older version exhibited. In a test run (using the given
test script, just with 28 replaced by 20), I get 18273 kN/sec with default,
and 21875 kN/sec when using taskset.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2014-10-08 16:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 19:44 Steinar H. Gunderson
2014-10-03 21:11 ` Marc Burkhardt
2014-10-03 21:14 ` Steinar H. Gunderson
2014-10-04 9:22 ` Marc Burkhardt
2014-10-04 13:41 ` Andi Kleen
2014-10-04 14:12 ` Steinar H. Gunderson
2014-10-04 14:50 ` Chuck Ebbert
2014-10-05 11:19 ` Steinar H. Gunderson
2014-10-08 15:37 ` bisected: futex regression >= 3.14 - was - " Mike Galbraith
2014-10-08 16:14 ` Thomas Gleixner
2014-10-08 16:45 ` Steinar H. Gunderson [this message]
2014-10-08 17:52 ` Mike Galbraith
2014-10-08 16:23 ` Steinar H. Gunderson
2014-10-08 17:04 ` Linus Torvalds
2014-10-08 17:05 ` Steinar H. Gunderson
2014-10-08 17:59 ` Mike Galbraith
2014-10-24 15:25 ` Thomas Gleixner
2014-10-24 16:38 ` Mike Galbraith
2014-10-26 10:39 ` Steinar H. Gunderson
2014-10-26 13:16 ` Mike Galbraith
2014-10-26 13:58 ` Mike Galbraith
2014-10-26 14:11 ` Steinar H. Gunderson
2014-10-26 14:41 ` Mike Galbraith
2014-10-27 10:05 ` Mike Galbraith
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=20141008164557.GB38790@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.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
all inboxes | Powered by JetHome®