From: Steven Rostedt <rostedt@goodmis.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <williams@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC PATCH RT] rwsem: The return of multi-reader PI rwsems
Date: Thu, 10 Apr 2014 10:32:55 -0400 [thread overview]
Message-ID: <20140410103255.2eba08c6@gandalf.local.home> (raw)
In-Reply-To: <1397140123.5137.99.camel@marge.simpson.net>
On Thu, 10 Apr 2014 16:28:43 +0200
Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
> On Thu, 2014-04-10 at 16:18 +0200, Mike Galbraith wrote:
> > On Wed, 2014-04-09 at 15:19 -0400, Steven Rostedt wrote:
> >
> > > If you have any benchmark on large machines I would be very happy if
> > > you could test this patch against the unpatched version of -rt.
> >
> > Too bad I don't have (and know how to use) specjbb.
> >
> > I dug up old vmark, thinking I'd be able to get some halfway useful
> > relative numbers from it, but that was a waste of a day. The thing
> > performs so badly on 40 core box that rt _beats_ nopreempt, and after 2
> > nodes, you're going backward. 40 Westmere EX cores does a whopping ~2.5
> > * dinky old Q6600 box throughput.
>
> P.S. What I didn't see was any sign of a delta patched/unpatched..
> which may mean nothing at all :-/
Actually that at least means it didn't cause any regressions for you.
-- Steve
next prev parent reply other threads:[~2014-04-10 14:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 19:19 [RFC PATCH RT] rwsem: The return of multi-reader PI rwsems Steven Rostedt
2014-04-10 14:18 ` Mike Galbraith
2014-04-10 14:28 ` Mike Galbraith
2014-04-10 14:32 ` Steven Rostedt [this message]
2014-04-11 2:50 ` Mike Galbraith
2014-04-11 3:25 ` Steven Rostedt
2014-04-11 3:52 ` Mike Galbraith
2014-04-11 4:25 ` Mike Galbraith
2014-04-10 14:44 ` Clark Williams
2014-04-10 15:01 ` Steven Rostedt
2014-04-10 15:03 ` Sebastian Andrzej Siewior
2014-04-10 15:36 ` Peter Zijlstra
2014-04-10 19:17 ` Steven Rostedt
2014-04-10 20:48 ` Peter Zijlstra
2014-04-10 21:30 ` Paul E. McKenney
2014-04-10 22:02 ` Steven Rostedt
2014-04-10 15:38 ` Steven Rostedt
2014-04-11 21:39 ` Daniel Bristot de Oliveira
2014-04-10 17:42 ` [RFC PATCH RT V2] " Steven Rostedt
2014-04-11 2:35 ` [RFC PATCH RT V3] " Steven Rostedt
2014-04-11 12:47 ` Carsten Emde
2014-04-11 13:25 ` Steven Rostedt
2014-04-17 23:26 ` [RFC PATCH RT V4] " Steven Rostedt
2014-04-18 8:19 ` Ingo Molnar
2014-04-24 17:52 ` Steven Rostedt
2014-04-14 9:55 ` [RFC PATCH RT] " Ingo Molnar
2014-04-14 13:34 ` Steven Rostedt
2014-04-14 14:08 ` Peter Zijlstra
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=20140410103255.2eba08c6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
--cc=williams@redhat.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).