From: Tejun Heo <htejun@gmail.com>
To: Matthew Fredrickson <creslin@digium.com>
Cc: linux-kernel@vger.kernel.org, ris <ris@elsat.net.pl>
Subject: Re: High CPU usage with sata_nv
Date: Mon, 12 Feb 2007 12:09:32 -0800 [thread overview]
Message-ID: <45D0C97C.108@gmail.com> (raw)
In-Reply-To: <9d377bf8f83da4ca7935f5a69cde5bef@digium.com>
Matthew Fredrickson wrote:
> I have noticed something that might be related as well. I am working on
> a device driver that would have periodic data errors due to
> exceptionally long interrupt handling latency. I have come to the point
> that I suspect that it's the sata_nv driver, and now that we can't do
> the hdparm -u1 option for sata, it seems to be a bigger problem.
That's mostly off topic. libata configures DMA if at all possible and
fallback to PIO only after a lot of serious errors. Is your drive in
pio mode? Or does it happen even when in dma mode?
--
tejun
next prev parent reply other threads:[~2007-02-12 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070115164541.M22367@elsat.net.pl>
2007-01-15 16:54 ` High CPU usage with sata_nv 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 [this message]
[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 ` Robert Hancock
2007-02-21 15:28 ` Matthew Fredrickson
2007-02-21 18:04 ` Lee Revell
2007-02-22 2:34 ` Robert Hancock
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=45D0C97C.108@gmail.com \
--to=htejun@gmail.com \
--cc=creslin@digium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ris@elsat.net.pl \
/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;
as well as URLs for NNTP newsgroup(s).