All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Cc: fweisbec@gmail.com
Subject: Re: rcu_preempt running flat out on idle desktop.
Date: Wed, 8 May 2013 15:20:29 -0700	[thread overview]
Message-ID: <20130508222029.GR3648@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130508211759.GA6808@redhat.com>

On Wed, May 08, 2013 at 05:17:59PM -0400, Dave Jones wrote:
> On Wed, May 08, 2013 at 02:16:35PM -0700, Paul E. McKenney wrote:
>  > On Wed, May 08, 2013 at 04:56:33PM -0400, Dave Jones wrote:
>  > > On Wed, May 08, 2013 at 01:52:58PM -0700, Paul E. McKenney wrote:
>  > >  > On Wed, May 08, 2013 at 04:30:42PM -0400, Dave Jones wrote:
>  > > 
>  > >  > >   PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND 
>  > >  > >    10 root      20   0     0    0    0 S 200.0  0.0 185301:36 rcu_preempt
>  > >  > >   553 root      20   0  268m  76m 6764 S 200.0  2.6 144579:53 Xorg
>  > >  > >  1199 root      20   0     0    0    0 S 200.0  0.0 306:17.85 kworker/1:0
>  > >  > >   501 root      20   0     0    0    0 S 200.0  0.0   4471:03 kworker/0:2
>  > >  > >    12 root      20   0     0    0    0 S 200.0  0.0  67277:16 rcuop/1
>  > >  > >  1237 davej     20   0  535m  15m 8484 S 200.0  0.5   3645:16 Terminal
>  > >  > >   859 davej     20   0  117m 3036 1336 S 200.0  0.1   1986:55 htop
>  > >  > > 
>  > >  > > There are a lot of processes allegedly using "200%" of CPU time, a handful
>  > >  > > in the "196%" range, and then a bunch at 0.
>  > >  > 
>  > >  > Yow!!!  185301 minutes is 128 days, which is a truly impressive amount of
>  > >  > CPU time to accumulate in a few short hours.
>  > > 
>  > > perf top doesn't show anything out of the ordinary. Just as an idle desktop
>  > > should behave, it's spending a bunch of time in delay_tsc.
>  > > 
>  > >  > This is 3.9, or Linus's current tree?  I am guessing the latter, but
>  > >  > figured I should ask.
>  > > 
>  > > Yeah, the latter. (v3.9-11572-g5af43c2)
>  > 
>  > Do you have CONFIG_NO_HZ_FULL=y?  We just might have a bug in tickless
>  > CPU-time accounting...
> 
> I never saw a new config option I didn't like.

;-) ;-) ;-)

> CONFIG_NO_HZ_FULL=y
> CONFIG_NO_HZ_FULL_ALL=y

Adding Frederic on CC...

							Thanx, Paul


  reply	other threads:[~2013-05-08 22:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 20:30 rcu_preempt running flat out on idle desktop Dave Jones
2013-05-08 20:52 ` Paul E. McKenney
2013-05-08 20:56   ` Dave Jones
2013-05-08 21:16     ` Paul E. McKenney
2013-05-08 21:17       ` Dave Jones
2013-05-08 22:20         ` Paul E. McKenney [this message]
2013-05-09  9:04     ` Frederic Weisbecker
2013-05-09  9:20       ` Ingo Molnar
2013-05-09 21:02 ` Frederic Weisbecker
2013-05-09 21:10   ` Dave Jones
2013-05-14  1:21     ` Frederic Weisbecker
2013-06-06 15:31       ` Dave Jones
2013-06-06 15:43         ` Frederic Weisbecker
2013-06-06 23:10           ` Dave Jones
2013-06-12 15:34           ` Dave Jones
2013-06-20 19:10             ` Dave Jones
2013-06-23 10:58               ` Ingo Molnar
2013-07-01 12:10                 ` Frederic Weisbecker

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=20130508222029.GR3648@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=davej@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.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 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.