From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
tglx@linutronix.de
Subject: Re: [tip:core/rcu] Revert "rcu: Decrease memory-barrier usage based on semi-formal proof"
Date: Thu, 26 May 2011 10:43:01 -0700 [thread overview]
Message-ID: <20110526174301.GA9649@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110526142553.GA2386@linux.vnet.ibm.com>
On Thu, May 26, 2011 at 07:25:53AM -0700, Paul E. McKenney wrote:
> On Thu, May 26, 2011 at 08:13:48AM +0200, Ingo Molnar wrote:
> >
> > * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> >
> > > rcu: Start RCU kthreads in TASK_INTERRUPTIBLE state
> > >
> > > Upon creation, kthreads are in TASK_UNINTERRUPTIBLE state, which can
> > > result in softlockup warnings. Because some of RCU's kthreads can
> > > legitimately be idle indefinitely, start them in TASK_INTERRUPTIBLE
> > > state in order to avoid those warnings.
> > >
> > > Suggested-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >
> > this should also solve load average artifacts - do not
> > TASK_UNINTERRUPTIBLE tasks skew the load upwards?
>
> Quite possibly -- in this case the artifacts would appear just after
> boot, and would disappear as soon as the RCU kthreads had something
> to do.
By the way, how would you like to proceed with the fixes thus far?
I have put them on -rcu for -next testing, FWIW.
Thanx, Paul
next prev parent reply other threads:[~2011-05-26 17:43 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-80d02085d99039b3b7f3a73c8896226b0cb1ba07@git.kernel.org>
2011-05-20 21:04 ` Yinghai Lu
2011-05-20 22:42 ` Paul E. McKenney
2011-05-20 23:09 ` Yinghai Lu
2011-05-20 23:14 ` Paul E. McKenney
2011-05-20 23:16 ` Yinghai Lu
2011-05-20 23:49 ` Paul E. McKenney
2011-05-21 0:02 ` Yinghai Lu
2011-05-21 13:18 ` Paul E. McKenney
2011-05-21 14:08 ` Paul E. McKenney
2011-05-23 20:14 ` Yinghai Lu
2011-05-23 21:25 ` Paul E. McKenney
2011-05-23 22:01 ` Yinghai Lu
2011-05-23 22:55 ` Yinghai Lu
2011-05-23 22:58 ` Yinghai Lu
2011-05-24 1:18 ` Paul E. McKenney
2011-05-24 1:26 ` Yinghai Lu
2011-05-24 1:35 ` Paul E. McKenney
2011-05-24 21:23 ` Yinghai Lu
2011-05-25 0:05 ` Paul E. McKenney
2011-05-25 0:13 ` Yinghai Lu
2011-05-25 4:46 ` Paul E. McKenney
2011-05-25 7:24 ` Ingo Molnar
2011-05-25 20:48 ` Paul E. McKenney
2011-05-25 7:18 ` Ingo Molnar
2011-05-25 0:16 ` Paul E. McKenney
2011-05-25 0:10 ` Yinghai Lu
2011-05-25 4:52 ` Paul E. McKenney
2011-05-25 7:27 ` Ingo Molnar
2011-05-25 20:47 ` Paul E. McKenney
2011-05-25 20:52 ` Ingo Molnar
2011-05-25 22:15 ` Yinghai Lu
2011-05-25 22:34 ` Paul E. McKenney
2011-05-25 22:49 ` Yinghai Lu
2011-05-26 1:13 ` Paul E. McKenney
2011-05-26 1:30 ` Paul E. McKenney
2011-05-26 6:13 ` Ingo Molnar
2011-05-26 14:25 ` Paul E. McKenney
2011-05-26 17:43 ` Paul E. McKenney [this message]
2011-05-26 20:26 ` Ingo Molnar
2011-05-26 15:08 ` Yinghai Lu
2011-05-26 16:28 ` Paul E. McKenney
2011-05-28 1:04 ` Paul E. McKenney
2011-05-28 4:03 ` Yinghai Lu
2011-05-28 6:38 ` Paul E. McKenney
2011-05-24 1:12 ` 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=20110526174301.GA9649@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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