linux-kernel - Re: [PATCH 1/3] Make the IDE DMA timeout modifiable

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:	Fri, 13 Jul 2007 11:12:18 -0400
From:	Mark Lord <liml@....ca>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Sergei Shtylyov <sshtylyov@...mvista.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	Suleiman Souhlal <ssouhlal@...ebsd.org>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] Make the IDE DMA timeout modifiable

Alan Cox wrote:
> O> >>    BTW, why the timeout is so damn long? 2*WAIT_CMD is 20 secs, and if DMA is 
>>>> not complete or interrupt pending, it may wait 10 more secs...
>>> I really don't remember... :)
>>> Maybe Mark or Alan could help with figuring this out.
>>     They also have probably forgotten. :-)
> 
> Because that value seemed to work ok. Mark set the timeouts way back in
> history and I never touched most of them.

I've lost the original question from this thread, but the idea of the longish
timeouts was that drive *may* be spun down ("standby"), and thus have to spin
up again to complete media commands.  Back then, drives were much slower at
spinning up than nowadays, and the ATA spec says to allow up to 30 seconds.

So..
-
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/