From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Tibor Billes <tbilles@gmx.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unusually high system CPU usage with recent kernels
Date: Tue, 1 Oct 2013 13:27:56 -0700 [thread overview]
Message-ID: <20131001202756.GK5790@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130914135951.288070@gmx.com>
On Sat, Sep 14, 2013 at 03:59:51PM +0200, Tibor Billes wrote:
> > From: Paul E. McKenney Sent: 09/13/13 02:19 AM
> > On Wed, Sep 11, 2013 at 08:46:04AM +0200, Tibor Billes wrote:
> > > > From: Paul E. McKenney Sent: 09/09/13 10:44 PM
[ . . . ]
> > > Sure. The attached tar file contains traces of good kernels. The first is with
> > > version 3.9.7 (no patch applied) which was the last stable kernel I tried and
> > > didn't have this issue. The second is version 3.11 with your fix applied.
> > > Judging by the size of the traces, 3.11.0+ is still doing more work than
> > > 3.9.7.
> >
> > Indeed, though quite a bit less than the problematic traces.
> >
> > Did you have all three patches applied to 3.11.0, or just the last one?
> > If the latter, could you please try it with all three?
>
> Only the last one was applied to 3.11.0. The attachement now contains the
> RCU trace with all thee applied. It seems to be smaller in size, but still
> not close to 3.9.7.
>
> > > > > I'm not sure about LKML policies about attaching not-so-small files to
> > > > > emails, so I've dropped LKML from the CC list. Please CC the mailing
> > > > > list in your reply.
> > > >
> > > > Done!
> > > >
> > > > Another approach is to post the traces on the web and send the URL to
> > > > LKML. But whatever works for you is fine by me.
> > >
> > > Sending directly to you won again :) Could you please CC the list in your
> > > reply?
> >
> > Done! ;-)
>
> Could you please CC the list in your reply again? :)
This trace is quite strange -- there are a number of processes that sleep
and then wake up almost immediately, as in within a microsecond or so.
I don't know why they would be doing that, and I also cannot think of
what RCU might be doing to make them do that.
I am unfortunately out of ideas on this one.
Thanx, Paul
next parent reply other threads:[~2013-10-01 20:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130914135951.288070@gmx.com>
2013-10-01 20:27 ` Paul E. McKenney [this message]
2013-10-06 8:42 Unusually high system CPU usage with recent kernels Tibor Billes
-- strict thread matches above, loose matches on Subject: below --
2013-09-28 14:13 Tibor Billes
[not found] <20130911064605.288090@gmx.com>
2013-09-13 0:19 ` Paul E. McKenney
[not found] <20130909194737.288090@gmx.com>
2013-09-09 20:44 ` Paul E. McKenney
2013-09-08 17:22 Tibor Billes
2013-09-08 18:43 ` Paul E. McKenney
2013-09-03 21:11 Tibor Billes
2013-09-03 22:16 ` Paul E. McKenney
2013-09-07 0:23 ` Paul E. McKenney
2013-08-30 14:46 Tibor Billes
2013-08-27 20:05 Tibor Billes
2013-08-30 1:24 ` Paul E. McKenney
2013-08-25 19:50 Tibor Billes
2013-08-26 4:28 ` Paul E. McKenney
2013-08-24 20:30 Tibor Billes
2013-08-24 19:59 Tibor Billes
2013-08-24 21:03 ` Paul E. McKenney
2013-08-23 13:20 Tibor Billes
2013-08-24 0:18 ` Paul E. McKenney
2013-08-21 21:05 Tibor Billes
2013-08-21 22:09 ` Paul E. McKenney
2013-08-21 18:14 Tibor Billes
2013-08-21 19:12 ` Paul E. McKenney
2013-08-20 20:52 Tibor Billes
2013-08-20 21:43 ` Paul E. McKenney
2013-08-20 6:01 Tibor Billes
2013-08-20 14:53 ` 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=20131001202756.GK5790@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tbilles@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.