From: Dimitri Sivanich <sivanich@sgi.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <ak@suse.de>,
Jes Sorensen <jes@sgi.com>
Subject: Re: [PATCH] Migration of Standard Timers
Date: Tue, 19 Sep 2006 11:41:59 -0500 [thread overview]
Message-ID: <20060919164159.GC26863@sgi.com> (raw)
In-Reply-To: <1158683617.11682.14.camel@mindpipe>
On Tue, Sep 19, 2006 at 12:33:37PM -0400, Lee Revell wrote:
> Which driver or subsystem is doing 100s of usecs of work in a timer?
The longest one I've captured so far results from:
rsp rip Function (args)
======================= <nmi>
0xffff810257822fd8 0xffffffff803a0e94 rt_check_expire+0x8c
======================= <interrupt>
0xffff81025781fee8 0xffffffff803a0e08 rt_check_expire
0xffff81025781ff08 0xffffffff802386b3 run_timer_softirq+0x133
0xffff81025781ff38 0xffffffff80235262 __do_softirq+0x5e
0xffff81025781ff68 0xffffffff8020a958 call_softirq+0x1c
0xffff81025781ff80 0xffffffff8020bea7 do_softirq+0x2c
0xffff81025781ff90 0xffffffff80235142 irq_exit+0x48
> Shouldn't another mechanism like a workqueue be used instead?
Not quite sure what you're asking here.
next prev parent reply other threads:[~2006-09-19 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 15:29 [PATCH] Migration of Standard Timers Dimitri Sivanich
2006-09-19 16:33 ` Lee Revell
2006-09-19 16:41 ` Dimitri Sivanich [this message]
2006-09-19 16:57 ` Lee Revell
2006-09-22 19:16 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 13:29 [PATCH] Migration of standard timers Dimitri Sivanich
2006-09-14 14:11 ` Jes Sorensen
2006-09-14 14:30 ` Dimitri Sivanich
2006-09-15 6:06 ` Andrew Morton
2006-09-15 16:39 ` Thomas Gleixner
2006-09-15 16:58 ` Dimitri Sivanich
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=20060919164159.GC26863@sgi.com \
--to=sivanich@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=tglx@linutronix.de \
/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