From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 10:58:50 -0400 [thread overview]
Message-ID: <20110331145850.GA10163@redhat.com> (raw)
In-Reply-To: <AANLkTikP5edK=YSRx7zuNqyfwez8qEHpFumYun6GOPxu@mail.gmail.com>
On Wed, Mar 30, 2011 at 10:32:11PM -0700, Linus Torvalds wrote:
> 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.
ok, a bit more interesting ?
- 17.67% kworker/0:1 [kernel.kallsyms] [k] read_hpet
- read_hpet
- 76.07% timekeeping_get_ns
- ktime_get
- 64.02% tick_dev_program_event
tick_program_event
hrtimer_interrupt
smp_apic_timer_interrupt
+ apic_timer_interrupt
- 35.30% sched_clock_tick
scheduler_tick
update_process_times
tick_sched_timer
__run_hrtimer
hrtimer_interrupt
smp_apic_timer_interrupt
- apic_timer_interrupt
+ 65.70% _raw_spin_unlock_irqrestore
+ 27.33% _raw_spin_unlock_irq
+ 1.16% lock_acquire
+ 1.16% put_ldisc
+ 1.16% process_one_work
+ 1.16% lock_release
+ 0.78% worker_thread
+ 0.58% _raw_spin_lock_irqsave
+ 0.55% tick_sched_timer
- 23.82% do_timer
tick_do_update_jiffies64
tick_sched_timer
__run_hrtimer
hrtimer_interrupt
smp_apic_timer_interrupt
- apic_timer_interrupt
+ 63.46% _raw_spin_unlock_irqrestore
+ 22.98% _raw_spin_unlock_irq
+ 3.50% put_ldisc
+ 3.28% lock_acquire
btw, I left this on overnight capturing the output of /proc/loadavg
it didn't drop off at all, and this morning the laptop is almost too
hot to hold.
Dave
next prev parent reply other threads:[~2011-03-31 14:59 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
2011-03-31 14:58 ` Dave Jones [this message]
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=20110331145850.GA10163@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--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 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.