From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Chuck Ebbert <cebbert@redhat.com>, Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: libata timeouts when stressing a Samsung HDD
Date: Wed, 11 Feb 2009 17:29:43 -0500 [thread overview]
Message-ID: <49935157.6020002@rtr.ca> (raw)
In-Reply-To: <49934D24.1050204@garzik.org>
Jeff Garzik wrote:
> Mark Lord wrote:
>> I wonder if it's just a case of too short a timeout on the cache flushes?
>
> The answer in general to this question has always been "yes".....
>
> Unless this has changed in the past year, the worst case for SATA cache
> flush can definitely exceed 30 seconds... it is unbounded as defined in
> the spec, and unbounded in practice as well.
..
But I don't think we've yet seen a proven case of it taking too long
for the current libata timeouts. Unless it's happening now.
T'would be good to find out.. Chuck?
next prev parent reply other threads:[~2009-02-11 22:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 21:40 libata timeouts when stressing a Samsung HDD Chuck Ebbert
2009-02-11 1:30 ` Tejun Heo
2009-02-11 4:08 ` Mark Lord
2009-02-11 20:29 ` Chuck Ebbert
2009-02-11 22:03 ` Mark Lord
2009-02-11 22:11 ` Jeff Garzik
2009-02-11 22:29 ` Mark Lord [this message]
2009-02-11 22:54 ` Chuck Ebbert
2009-02-12 16:10 ` Mark Lord
2009-02-12 16:13 ` Mark Lord
2009-02-16 3:12 ` Tejun Heo
2009-02-16 21:30 ` Chuck Ebbert
2009-02-19 6:21 ` Tejun Heo
2009-02-19 16:41 ` Greg Freemyer
2009-02-20 0:33 ` Tejun Heo
2009-02-12 4:28 ` Robert Hancock
2009-02-19 15:27 ` Mark Lord
2009-02-20 0:32 ` Tejun Heo
2009-02-20 2:52 ` Robert Hancock
2009-02-20 3:26 ` Tejun Heo
2009-03-01 19:31 ` Robert Hancock
2009-03-01 20:28 ` Alan Cox
2009-02-11 20:24 ` Chuck Ebbert
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=49935157.6020002@rtr.ca \
--to=liml@rtr.ca \
--cc=cebbert@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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.