From: Ric Wheeler <ric@emc.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: "Eric D. Mudama" <edmudama@gmail.com>, Mark Lord <liml@rtr.ca>,
Tejun Heo <htejun@gmail.com>, Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: reduce ATA command timeout to 7secs
Date: Sat, 03 Feb 2007 18:34:40 -0500 [thread overview]
Message-ID: <45C51C10.3010801@emc.com> (raw)
In-Reply-To: <20070202184743.1516d1f9@localhost.localdomain>
Alan wrote:
>> generic PC market, as opposed to "RAID edition" or "MaxLine" or
>> similar branding from other vendors, where the firmware may have been
>> specifically optimized for quicker command completion, quicker status
>> reporting and less exhaustive error recovery. Many linux users I
>
> Is there a way to detect RAID drives with this kind of timing, or does
> someone need to take a baseball bat into the standards committee meeting
> and add an identify field that gives command and "long command" timeouts
> in seconds ?
We figure it out by testing lots & lots of drives ;-)
>
> If we can detect the "fast fail" drives (initially by say ident string
> components) lets do it and the people who care can buy the right product
> for the job.
I don't think that there is any kind of feature field...
>
> Alan
>
next prev parent reply other threads:[~2007-02-03 23:34 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 [this message]
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=45C51C10.3010801@emc.com \
--to=ric@emc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=edmudama@gmail.com \
--cc=htejun@gmail.com \
--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 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).