From: Ben Hutchings <ben@decadent.org.uk>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: tip-bot for Tim Chen <tipbot@zytor.com>,
suruchi.a.kadu@intel.com, linux-kernel@vger.kernel.org,
sbohrer@rgmadvisors.com, peterz@infradead.org, mingo@kernel.org,
tglx@linutronix.de, doug.nelson@intel.com,
torvalds@linux-foundation.org, tim.c.chen@linux.intel.com,
hpa@zytor.com, stable@vger.kernel.org,
Clark Williams <williams@redhat.com>
Subject: Re: [tip:sched/core] sched/rt: Reduce rq lock contention by eliminating locking of non-feasible target
Date: Tue, 03 Mar 2015 21:12:57 +0000 [thread overview]
Message-ID: <1425417177.4190.44.camel@decadent.org.uk> (raw)
In-Reply-To: <20150224111247.2ca122c3@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
On Tue, 2015-02-24 at 11:12 -0500, Steven Rostedt wrote:
> On Sun, 1 Feb 2015 09:52:24 -0800
> tip-bot for Tim Chen <tipbot@zytor.com> wrote:
>
> > Commit-ID: 80e3d87b2c5582db0ab5e39610ce3707d97ba409
> > Gitweb: http://git.kernel.org/tip/80e3d87b2c5582db0ab5e39610ce3707d97ba409
> > Author: Tim Chen <tim.c.chen@linux.intel.com>
> > AuthorDate: Fri, 12 Dec 2014 15:38:12 -0800
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Fri, 30 Jan 2015 19:38:49 +0100
> >
> > sched/rt: Reduce rq lock contention by eliminating locking of non-feasible target
> >
> > This patch adds checks that prevens futile attempts to move rt tasks
> > to a CPU with active tasks of equal or higher priority.
> >
> > This reduces run queue lock contention and improves the performance of
> > a well known OLTP benchmark by 0.7%.
> >
> > Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > Cc: Shawn Bohrer <sbohrer@rgmadvisors.com>
> > Cc: Suruchi Kadu <suruchi.a.kadu@intel.com>
> > Cc: Doug Nelson<doug.nelson@intel.com>
> > Cc: Steven Rostedt <rostedt@goodmis.org>
> > Cc: Linus Torvalds <torvalds@linux-foundation.org>
> > Link: http://lkml.kernel.org/r/1421430374.2399.27.camel@schen9-desk2.jf.intel.com
> > Signed-off-by: Ingo Molnar <mingo@kernel.org>
>
> I see this has been added to mainline already. I think this should go
> to stable as well. As far back as it applies. I'll even add this to the
> stable-rt if need be. But I rather pull it into stable-rt via the
> stable branches.
[...]
I've queued this up for 3.2, thanks.
Ben.
--
Ben Hutchings
The world is coming to an end. Please log off.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-03-03 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 19:01 [PATCH] Repost sched-rt: " Tim Chen
2015-01-06 19:30 ` Peter Zijlstra
2015-01-15 17:13 ` Tim Chen
2015-01-16 1:58 ` Steven Rostedt
2015-01-16 17:46 ` Tim Chen
2015-01-22 17:48 ` Tim Chen
2015-02-01 17:52 ` [tip:sched/core] sched/rt: " tip-bot for Tim Chen
2015-02-24 16:12 ` Steven Rostedt
2015-03-03 21:12 ` Ben Hutchings [this message]
2015-04-09 1:17 ` Zefan Li
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=1425417177.4190.44.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=doug.nelson@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbohrer@rgmadvisors.com \
--cc=stable@vger.kernel.org \
--cc=suruchi.a.kadu@intel.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=tipbot@zytor.com \
--cc=torvalds@linux-foundation.org \
--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
Powered by JetHome