From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matteo Franchin <Matteo.Franchin@arm.com>,
Davidlohr Bueso <davidlohr@hp.com>,
Darren Hart <dvhart@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] futex: Ensure get_futex_key_refs() always implies a barrier
Date: Sat, 18 Oct 2014 18:15:29 +0200 [thread overview]
Message-ID: <1413648929.5367.25.camel@marge.simpson.net> (raw)
In-Reply-To: <CA+55aFydqk0NVcYHForRCXVJj_Tw+T+ZW9GikAmUXdOgdpGf5A@mail.gmail.com>
On Sat, 2014-10-18 at 08:28 -0700, Linus Torvalds wrote:
> On Fri, Oct 17, 2014 at 11:54 PM, Mike Galbraith
> <umgwanakikbuti@gmail.com> wrote:
> >
> > The barrier fixing up my problematic box smells a lot like evidence.
>
> Is this a "tested-by"? Did you actuallyu verify that the patch ends up
> fixing the problem you saw?
Yup, it definitely fixed it up.
Weird that it didn't show at all on the 2 socket 20 core box the problem
I was looking into was reported on, but was 100% busted on the similar 2
socket 28 core box I borrowed to have a peek, and only that box. My
(crippled/slow) 64 core DL980 was perfectly happy, as were my 3 home
boxen, not a peep from anywhere but that one 28 core box.
Hohum.. Tested-by: Mike Galbraith <umgwanakikbuti@gmail.com>
-Mike
next prev parent reply other threads:[~2014-10-18 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 16:38 Catalin Marinas
2014-10-18 6:54 ` Mike Galbraith
2014-10-18 7:09 ` Mike Galbraith
2014-10-18 15:28 ` Linus Torvalds
2014-10-18 16:15 ` Mike Galbraith [this message]
2014-10-18 7:33 ` Davidlohr Bueso
2014-10-18 19:58 ` Davidlohr Bueso
2014-10-18 20:50 ` Linus Torvalds
2014-10-19 2:16 ` Davidlohr Bueso
2014-10-20 9:11 ` Thomas Gleixner
2014-10-20 10:49 ` Catalin Marinas
2014-10-20 15:32 ` Linus Torvalds
2014-10-20 16:00 ` Catalin Marinas
2014-10-18 19:32 ` Darren Hart
2014-10-18 20:19 ` Davidlohr Bueso
2014-10-18 20:25 ` Darren Hart
2014-10-20 10:15 ` Catalin Marinas
2014-10-24 3:27 ` [PATCH] futex: Mention key referencing differences between shared and private futexes Davidlohr Bueso
2014-10-24 9:11 ` Catalin Marinas
2014-10-26 15:22 ` [tip:locking/urgent] " tip-bot for Davidlohr Bueso
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=1413648929.5367.25.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=Matteo.Franchin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=davidlohr@hp.com \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome