From: "Lee Revell" <rlrevell@joe-job.com>
To: "Matthew Fredrickson" <creslin@digium.com>
Cc: "Robert Hancock" <hancockr@shaw.ca>,
"Tejun Heo" <htejun@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: High CPU usage with sata_nv
Date: Wed, 21 Feb 2007 13:04:12 -0500 [thread overview]
Message-ID: <75b66ecd0702211004x49c4613cqe26d4871ec1453e8@mail.gmail.com> (raw)
In-Reply-To: <0c69abe94bbc69f652831a64ad77d0cb@digium.com>
On 2/21/07, Matthew Fredrickson <creslin@digium.com> wrote:
> It's a 2.6.18 kernel. What we're seeing (by means of the interrupt pin
> on another card) is extremely large interrupt latency (measured from
> the time the interrupt pin goes low to the first couple lines of code
> in the IRQ handler to clear it) occasionally, in the order of 500-700
> microseconds. I figured it was some other driver on the system
> disabling irqs for a long period of time, but it's difficult to trace
> what might be doing that.
Apply the -rt kernel patch and enable the latency tracer, it will tell
you what code path is responsible.
Lee
next prev parent reply other threads:[~2007-02-21 18:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.1OWRIIUBXsZOXflsGLA+7d4YCc0@ifi.uio.no>
[not found] ` <fa.A0XBTh7eCfsh11d3AhMO71/4xQU@ifi.uio.no>
[not found] ` <fa.fCm35VohC2wt9vlkg94Ru7me4ic@ifi.uio.no>
[not found] ` <fa.qDqCne4pXntL0PolSS2j8t4py3g@ifi.uio.no>
[not found] ` <fa.8TboLRab6f7zzIWFr/JPM6q04Zo@ifi.uio.no>
[not found] ` <fa.PMqnzxUBiShkWV4h9SiztNIwYc0@ifi.uio.no>
2007-02-21 3:43 ` High CPU usage with sata_nv Robert Hancock
2007-02-21 15:28 ` Matthew Fredrickson
2007-02-21 18:04 ` Lee Revell [this message]
2007-02-22 2:34 ` Robert Hancock
[not found] <20070115164541.M22367@elsat.net.pl>
2007-01-15 16:54 ` ris
2007-01-15 18:26 ` Frederik Deweerdt
2007-01-15 22:28 ` ris
2007-01-22 3:40 ` Tejun Heo
2007-02-11 22:31 ` ris
2007-02-12 6:49 ` Tejun Heo
2007-02-12 14:11 ` ris
2007-02-12 16:18 ` Tejun Heo
2007-02-12 20:02 ` Matthew Fredrickson
2007-02-12 20:09 ` 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=75b66ecd0702211004x49c4613cqe26d4871ec1453e8@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=creslin@digium.com \
--cc=hancockr@shaw.ca \
--cc=htejun@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.