From: Steven Rostedt <rostedt@goodmis.org>
To: paulmck@linux.vnet.ibm.com
Cc: Josh Boyer <jwboyer@redhat.com>,
linux-kernel@vger.kernel.org, kernel-team@fedoraproject.org
Subject: Re: Large slowdown with 'x86: Avoid invoking RCU when CPU is idle'
Date: Fri, 24 Feb 2012 12:20:44 -0500 [thread overview]
Message-ID: <1330104044.25686.165.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20120224165130.GB2399@linux.vnet.ibm.com>
On Fri, 2012-02-24 at 08:51 -0800, Paul E. McKenney wrote:
> But after looking this over, Steven Rostedt's three-patch set should
> suffice:
>
> https://lkml.org/lkml/2012/2/7/231
>
> The reason that mine are not needed is that the problematic code is
> called -only- from idle, not from process context, and also that the
> problematic code is tracing. My patch #45 is required for code that is
> called from both process context and from idle. My patch #46 is required
> for non-tracing uses of RCU from within the idle loop -- along with TBD
> patches to wrap those uses of RCU in the RCU_NONIDLE() macro.
>
> So again, in your particular case of x86's power-tracing features,
> Steven Rostedt's three-patch series called out above should be all
> that you need.
>
> I have CCed Steven in case there is some prerequisite to his patch set.
The above link is the RFC, it probably still suffices, but the patches
that are going into mainline are here:
https://lkml.org/lkml/2012/2/13/530
https://lkml.org/lkml/2012/2/13/525
https://lkml.org/lkml/2012/2/13/524
The above is the order to apply them, (patch 3, 4, and 5) even though
they arrived to LKML out of order.
-- Steve
prev parent reply other threads:[~2012-02-24 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 1:16 Josh Boyer
2012-02-22 1:32 ` Paul E. McKenney
2012-02-22 1:42 ` Josh Boyer
2012-02-24 14:40 ` Josh Boyer
2012-02-24 16:17 ` Paul E. McKenney
2012-02-24 16:27 ` Josh Boyer
2012-02-24 16:51 ` Paul E. McKenney
2012-02-24 17:20 ` Steven Rostedt [this message]
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=1330104044.25686.165.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=jwboyer@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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
all inboxes | Powered by JetHome®