public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@redhat.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, kernel-team@fedoraproject.org
Subject: Large slowdown with 'x86: Avoid invoking RCU when CPU is idle'
Date: Tue, 21 Feb 2012 20:16:53 -0500	[thread overview]
Message-ID: <20120222011652.GE23186@zod.bos.redhat.com> (raw)

Hi Paul,

Over in Fedora land, I applied your patch from this thread:

https://lkml.org/lkml/2012/1/24/441

to our 3.3-rc3/rc4 based rawhide kernels.  The intention was to solve an
RCU issue that was very similar to what Eric originally reported, and
the RCU splat did indeed go away[1].

However, we then got a few reports of kernels containing that patch
being extremely slow.  When the patch was dropped, the slowness goes
away according to one reporter.  The details can be found in this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=795050

The slowness doesn't seem to hit everyone, and in my local testing
things seem to be working just fine.  The reporters have widely varying
hardware as well, so it doesn't seem machine specific.

Perhaps I misdiagnosed the original issue, or perhaps I missed something
else that needs to be applied prior to this but I thought I would point
this out in case you had any ideas.

josh

[1] https://bugzilla.redhat.com/show_bug.cgi?id=789641

             reply	other threads:[~2012-02-22  1:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22  1:16 Josh Boyer [this message]
2012-02-22  1:32 ` Large slowdown with 'x86: Avoid invoking RCU when CPU is idle' 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

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=20120222011652.GE23186@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