From: Daniel Pittman <daniel@rimspace.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Disabling ATAPI retry?
Date: Fri, 07 Mar 2003 15:08:02 +1100 [thread overview]
Message-ID: <87k7fbq0nx.fsf@enki.rimspace.net> (raw)
In-Reply-To: <1046991672.17715.134.camel@irongate.swansea.linux.org.uk> (Alan Cox's message of "06 Mar 2003 23:01:12 +0000")
On 06 Mar 2003, Alan Cox wrote:
> On Thu, 2003-03-06 at 20:58, kelleycook@wideopenwest.com wrote:
>> Is there a boot parameter or a runtime command that can tell
>> the linux IDE driver not to automatically retry on error.
>
> There isn't. You can always build a kernel set not to, but even then
> it takes the drive firmware a sizeable time to retry a block.
Hrm. Is this something that is likely to be introduced at some point?
My interest lies in the fact that I use a Linux based DVD player which
locked up for around twenty minutes the other night trying to read a
dozen bad blocks on a DVD with a single scratch...
Being able to reduce that time lag to a minimum, even if it left the
hardware delays, would be great -- even if it was only for ATAPI
devices.
The biggest slowdown was the kernel retrying each block a number of
times, then performing a full ATAPI bus reset before giving up.
Daniel
--
Why could one never do a natural thing without having to
screen it behind a structure of artifice?
-- Edith Wharton, _House of Mirth_
next prev parent reply other threads:[~2003-03-07 3:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 20:58 kelleycook
2003-03-06 23:01 ` Alan Cox
2003-03-07 4:08 ` Daniel Pittman [this message]
2003-03-07 13:06 ` Alan Cox
2003-03-08 21:18 ` IBM^H^H^HHitachi disk tools (was Re: Disabling ATAPI retry?) Barry K. Nathan
2003-03-06 22:38 Disabling ATAPI retry? Mikael Pettersson
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=87k7fbq0nx.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®