From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jens Axboe <axboe@suse.de>
Subject: Re: [PATCH] libata: reduce ATA command timeout to 7secs
Date: Sat, 03 Feb 2007 13:45:21 +0900 [thread overview]
Message-ID: <45C41361.3060409@gmail.com> (raw)
In-Reply-To: <45C362ED.3040600@rtr.ca>
[cc'ing Jens, hello]
Mark Lord wrote:
> 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.
>
> Good patch, LONG overdue.
>
> But 7 seconds is too short. I have drives here now that
> take slightly more than 7 seconds to report media errors.
>
> With this patch, libata will timeout/reset the drive just before
> it had a chance to tell us why it was taking too long.
>
> The result would be that we might lose data unnecessarily,
> especially in combination with the current SCSI policy of
> blindly failing the entire request when only one sector was bad.
Timeout doesn't indicate media error, so SCSI will retry the command
several times. So, those two don't interact.
> I've used 10 second timeouts with 100% success over the past 14 years,
> which allows just enough margin (+2) for drives to finish their internal
> retries and report back.
>
> NACK to 7, ACK to 10 seconds.
Hmmm... I don't care whether 7 or 10. The biggest reason I chose 7 was
because somebody told me that that's the de-facto default ATA command
timeout && the other os is using it. I faintly remembers that it was
yourself or Jens. Or I might be just imagining things again. :-)
Jens, what do you think about this?
Thanks.
--
tejun
prev parent reply other threads:[~2007-02-03 4:45 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
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 [this message]
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=45C41361.3060409@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--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 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.