From: Mike Galbraith <bitbucket@online.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] rcu: Eliminate softirq processing from rcutree
Date: Mon, 23 Dec 2013 06:12:39 +0100 [thread overview]
Message-ID: <1387775559.5369.20.camel@marge.simpson.net> (raw)
In-Reply-To: <1387773533.5369.16.camel@marge.simpson.net>
On Mon, 2013-12-23 at 05:38 +0100, Mike Galbraith wrote:
> On Sun, 2013-12-22 at 09:57 +0100, Mike Galbraith wrote:
> > I'll let the box give
> > RCU something to do for a couple days. No news is good news.
>
> Ho ho hum, merry christmas, gift attached.
>
> I'll beat on virgin -rt7, see if it survives, then re-apply RCU patch
> and retest. This kernel had nohz_full enabled, along with Sebastian's
> pending -rt fix for same, so RCU patch was not only not running solo,
> box was running a known somewhat buggy config as well. Box was doing
> endless tbench 64 when it started stalling fwiw.
>
> -Mike
P.S.
virgin -rt7 doing tbench 64 + make -j64
[ 97.907960] perf samples too long (3138 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 103.047921] perf samples too long (5544 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
[ 181.561271] perf samples too long (10318 > 10000), lowering kernel.perf_event_max_sample_rate to 13000
[ 184.243750] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 1.084 msecs
[ 248.914422] perf samples too long (19719 > 19230), lowering kernel.perf_event_max_sample_rate to 7000
[ 382.116674] NOHZ: local_softirq_pending 10
[ 405.201593] perf samples too long (36824 > 35714), lowering kernel.perf_event_max_sample_rate to 4000
[ 444.704185] NOHZ: local_softirq_pending 08
[ 444.704208] NOHZ: local_softirq_pending 08
[ 444.704579] NOHZ: local_softirq_pending 08
[ 444.704678] NOHZ: local_softirq_pending 08
[ 444.705100] NOHZ: local_softirq_pending 08
[ 444.705980] NOHZ: local_softirq_pending 08
[ 444.705994] NOHZ: local_softirq_pending 08
[ 444.708315] NOHZ: local_softirq_pending 08
[ 444.710348] NOHZ: local_softirq_pending 08
[ 474.435582] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 1.096 msecs
[ 475.994055] perf samples too long (63124 > 62500), lowering kernel.perf_event_max_sample_rate to 2000
Those annoying perf gripes are generic, not -rt.
next prev parent reply other threads:[~2013-12-23 5:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 19:39 [PATCH] rcu: Eliminate softirq processing from rcutree Sebastian Andrzej Siewior
2013-12-22 3:07 ` Mike Galbraith
2013-12-22 8:57 ` Mike Galbraith
2013-12-23 4:38 ` Mike Galbraith
2013-12-23 5:12 ` Mike Galbraith [this message]
2014-01-24 19:46 ` Sebastian Andrzej Siewior
2014-01-25 5:20 ` Mike Galbraith
2013-12-24 19:36 ` Paul E. McKenney
2013-12-25 3:07 ` Mike Galbraith
2013-12-25 7:55 ` Paul E. McKenney
2013-12-25 17:37 ` Mike Galbraith
2014-01-17 17:14 ` Sebastian Andrzej Siewior
2014-01-18 3:25 ` Mike Galbraith
2014-01-24 19:50 ` Sebastian Andrzej Siewior
2014-01-25 5:12 ` Mike Galbraith
2014-01-27 5:10 ` Mike Galbraith
2014-01-27 16:54 ` Paul E. McKenney
2014-01-27 17:03 ` Mike Galbraith
2013-12-26 10:03 ` Mike Galbraith
2014-01-17 17:23 ` Sebastian Andrzej Siewior
2014-01-18 3:30 ` 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=1387775559.5369.20.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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