From: Ric Wheeler <ric@emc.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] libata: reduce ATA command timeout to 7secs
Date: Fri, 02 Feb 2007 08:25:35 -0500 [thread overview]
Message-ID: <45C33BCF.2040506@emc.com> (raw)
In-Reply-To: <20070202063748.GC1625@htj.dyndns.org>
Tejun Heo wrote:
>Both ATA and ATAPI devices used the default timeouts defined by SCSI
>high level driver. For both disks and ODDs, it was 30secs, which was
>way too long for disks. This patch makes most ATA commands time out
>after 7secs - the de facto ATA command timeout, while leaving ATAPI
>timeout at 30secs.
>
>Note that both normal commands and EH commands timeouts are adjusted
>to 7 secs, but cache flushses still have 30sec timeout. This is a
>side effect of the way sd makes use of sdev->timeout, but this is a
>good side effect in that ATA spec requires cache flushes are given
>longer timeout.
>
>
>
>
I am not sure that this is really a requirement that ATA (or S-ATA)
drives can meet. There are definitely error conditions that will exceed
7 seconds and take that 30 second time to respond.
If the drive is stuck in recovery mode and we retry too soon, we are
going to be likely to write off a perfectly good disk which would be a
huge downside ;-)
ric
next prev parent reply other threads:[~2007-02-02 13:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 6:37 [PATCH] libata: reduce ATA command timeout to 7secs Tejun Heo
2007-02-02 10:08 ` Alan
2007-02-02 11:49 ` Tejun Heo
2007-02-02 13:25 ` Ric Wheeler [this message]
2007-02-02 15:12 ` Tejun Heo
2007-02-02 15:39 ` Alan
2007-02-02 16:13 ` Mark Lord
2007-02-02 16:43 ` Eric D. Mudama
2007-02-02 18:47 ` Alan
2007-02-02 23:00 ` Eric D. Mudama
2007-02-03 23:34 ` Ric Wheeler
2007-02-03 4:31 ` Tejun Heo
2007-02-03 19:59 ` Alan
2007-02-03 19:50 ` Mark Lord
2007-02-02 16:12 ` Mark Lord
2007-02-03 4:45 ` 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=45C33BCF.2040506@emc.com \
--to=ric@emc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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 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).