linux-kernel - Re: High CPU usage with sata

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Feb 2007 09:28:17 -0600
From:	Matthew Fredrickson <creslin@...ium.com>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	Tejun Heo <htejun@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: High CPU usage with sata_nv


On Feb 20, 2007, at 9:43 PM, Robert Hancock wrote:

> 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.
>
> What kernel are you using? There were some complaints about latency 
> problems (the ATA status register read taking a ridiculous amount of 
> time to complete) on sata_nv previously, but 2.6.20 should eliminate 
> that problem at least on nForce4 chipsets..
>

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.

Matthew Fredrickson

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/