From: Peter Zijlstra <peterz@infradead.org>
To: paulmck@linux.vnet.ibm.com
Cc: "Alex,Shi" <alex.shi@intel.com>,
"Li, Shaohua" <shaohua.li@intel.com>, Ingo Molnar <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
"Chen, Tim C" <tim.c.chen@intel.com>,
rostedt@goodmis.org
Subject: Re: rcu: performance regression
Date: Tue, 14 Jun 2011 15:14:58 +0200 [thread overview]
Message-ID: <1308057298.19856.40.camel@twins> (raw)
In-Reply-To: <20110614130203.GF2264@linux.vnet.ibm.com>
On Tue, 2011-06-14 at 06:02 -0700, Paul E. McKenney wrote:
> > This commit also cause hackbench process mode performance dropping, and
> > Shaohua's patch do recovered this. But in hackbench testing, the vmstat
> > show context switch have some reduce. And perf tool show
> > root_domain->cpupri->prio_to_cpu[]->lock has contention with the commit.
>
> Steven, Peter, would any of the recent fixes address this lock contention?
No. People occasionally run into that thing, but given the constraints
on SCHED_FIFO SMP (run the n highest priority tasks on m cpus; n<=m)
there isn't really much we can do.
IIRC Chris Mason once proposed a lockless version, but that opened up
race windows, Steve might know the details better.
next prev parent reply other threads:[~2011-06-14 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 5:26 rcu: performance regression Shaohua Li
2011-06-14 8:13 ` Ingo Molnar
2011-06-14 12:56 ` Paul E. McKenney
2011-06-14 8:33 ` Alex,Shi
2011-06-14 11:37 ` Alex,Shi
2011-06-14 13:02 ` Paul E. McKenney
2011-06-14 13:07 ` Shi, Alex
2011-06-14 13:14 ` Peter Zijlstra [this message]
2011-06-14 13:18 ` Peter Zijlstra
2011-06-14 15:01 ` Paul E. McKenney
2011-06-14 15:10 ` Peter Zijlstra
2011-06-14 15:32 ` Paul E. McKenney
2011-06-14 12:43 ` Paul E. McKenney
2011-06-14 16:48 ` Paul E. McKenney
2011-06-14 20:50 ` Paul E. McKenney
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=1308057298.19856.40.camel@twins \
--to=peterz@infradead.org \
--cc=alex.shi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.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