From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Dave Jones <davej@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: excessive kworker activity when idle. (was Re: vma corruption in today's -git)
Date: Thu, 31 Mar 2011 11:21:35 -0300 [thread overview]
Message-ID: <20110331142135.GB25095@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTikP5edK=YSRx7zuNqyfwez8qEHpFumYun6GOPxu@mail.gmail.com>
Em Wed, Mar 30, 2011 at 10:32:11PM -0700, Linus Torvalds escreveu:
> On Wed, Mar 30, 2011 at 8:55 PM, Dave Jones <davej@redhat.com> wrote:
> > I tried that, and wasn't particularly enlightened.
> >
> > + 6.53% kworker/1:2 [kernel.kallsyms] [k] read_hpet
> > + 4.83% kworker/0:0 [kernel.kallsyms] [k] read_hpet
>
> Go into those, deeper into the callchain. That's how to see what the
> upper-level problem is - by seeing who actually calls it. The leafs
> themselves (where the time is obviously spent) don't tend to be very
> informative, no.
Yeah, please press 'E' since you're using the TUI, where you can expand
collapse callchains in all its levels.
Pressing 'E' will expand all of them, 'C' will collapse it all. Enter on
lines with a '+' will expand just that one, etc.
Press 'h' to get more help.
Or use 'perf report --stdio' and you'll get it all expanded and in plain
text.
- Arnaldo
next prev parent reply other threads:[~2011-03-31 14:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 4:09 vma corruption in today's -git Dave Jones
2011-03-29 4:19 ` Américo Wang
2011-03-29 4:26 ` Dave Jones
2011-03-29 4:22 ` Linus Torvalds
2011-03-31 3:09 ` excessive kworker activity when idle. (was Re: vma corruption in today's -git) Dave Jones
2011-03-31 3:34 ` Dave Jones
2011-03-31 3:44 ` Linus Torvalds
2011-03-31 4:08 ` Dave Jones
2011-03-31 15:53 ` Linus Torvalds
2011-03-31 16:21 ` Linus Torvalds
2011-03-31 21:38 ` Linus Torvalds
2011-03-31 14:59 ` Paul E. McKenney
2011-03-31 3:37 ` Linus Torvalds
2011-03-31 3:55 ` Dave Jones
2011-03-31 5:32 ` Linus Torvalds
2011-03-31 14:21 ` Arnaldo Carvalho de Melo [this message]
2011-03-31 14:58 ` Dave Jones
2011-03-31 15:03 ` Dave Jones
2011-03-31 15:09 ` Dave Jones
2011-03-31 15:45 ` Linus Torvalds
2011-03-31 15:25 ` Linus Torvalds
2011-03-31 15:49 ` Dave Jones
2011-03-31 15:58 ` Linus Torvalds
2011-03-31 16:13 ` Dave Jones
2011-03-31 6:56 ` Tejun Heo
2011-03-31 10:37 ` [PATCH] workqueue: document debugging tricks Florian Mickler
2011-03-31 11:41 ` Tejun Heo
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=20110331142135.GB25095@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox