From: Josh Boyer <jwboyer@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: 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 09:40:32 -0500 [thread overview]
Message-ID: <20120224144032.GA13903@zod.bos.redhat.com> (raw)
In-Reply-To: <20120222014242.GF23186@zod.bos.redhat.com>
On Tue, Feb 21, 2012 at 08:42:43PM -0500, Josh Boyer wrote:
> > And patch #47 in that series has been obsoleted by another series
> > from Steven Rostedt:
> >
> > https://lkml.org/lkml/2012/2/7/231
>
> Ok.
>
> > Hopefully these fix both splats and slowness.
>
> So again, I'm slightly confused on how RCU patches flow. Eric
> originally reported the bug for which you created the patch I applied
> against 3.3. The giant patch series above seems queued for 3.4.
>
> I don't see stable CC'd on 45-47, nor any of Steven's patches. I doubt
> I'd want to go applying the 47-patch series on 3.3 at the moment, and
> given you have these marked for 3.4 I don't think you do either.
> However, is there some kind of fix for the original bug report against
> 3.3?
I was being sincere when I asked the above questions. Could you
describe how you handle RCU patches across releases and if there is a
fix for the 3.3-rcX issue Eric reported that is going into 3.3?
I know you're quite busy, but I'd like to understand your thinking so I
know what to expect going forward.
josh
next prev parent reply other threads:[~2012-02-24 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 1:16 Large slowdown with 'x86: Avoid invoking RCU when CPU is idle' Josh Boyer
2012-02-22 1:32 ` Paul E. McKenney
2012-02-22 1:42 ` Josh Boyer
2012-02-24 14:40 ` Josh Boyer [this message]
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
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=20120224144032.GA13903@zod.bos.redhat.com \
--to=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