mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: liml@rtr.ca
Cc: hancockrwd@gmail.com, phdm@macqel.be, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH ide] : Increase WAIT_DRQ to support slow CF cards
Date: Wed, 02 Dec 2009 21:57:38 -0800 (PST)	[thread overview]
Message-ID: <20091202.215738.12118816.davem@davemloft.net> (raw)
In-Reply-To: <4AEC420A.9030502@rtr.ca>

From: Mark Lord <liml@rtr.ca>
Date: Sat, 31 Oct 2009 09:56:26 -0400

> Robert Hancock wrote:
> ..
>> This has come up before:
>> http://marc.info/?l=linux-ide&m=123064513313466&w=2
>> I think this timeout should not even exist. libata has no such timeout
>> (only the overall command completion timeout), and I can't find any
>> reference in current ATA specs to the device being required to raise
>> DRQ in any particular amount of time.
> ..
> 
> The reason for the original (20ms, then 50ms) timeout was this text
> from the ATA1 specification, long since outdated:
> 
>   -  Upon receipt of a Class 3 command, the drive sets BSY within 400 nsec,
>      sets  up the sector buffer for a write operation, sets DRQ within 20
>      msec, and clears BSY within 400 nsec of setting DRQ.

Ok, I'd like to resolve this as follows.  We had stated "at least
500msec for SSD drives" so I doubled it.

This should be a pretty safe change.  The only major side effect is
that if the device really does hang before setting DRQ it will take
a full second before we notice it.

Any major objections?

ide: Increase WAIT_DRQ to accomodate some CF cards and SSD drives.

Based upon a patch by Philippe De Muyter, and feedback from Mark
Lord and Robert Hancock.

As noted by Mark Lord, the outdated ATA1 spec specifies a 20msec
timeout for setting DRQ but lots of common devices overshoot this.

Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/include/linux/ide.h b/include/linux/ide.h
index e4135d6..0ec6129 100644
--- a/include/linux/ide.h
+++ b/include/linux/ide.h
@@ -125,8 +125,8 @@ struct ide_io_ports {
  * Timeouts for various operations:
  */
 enum {
-	/* spec allows up to 20ms */
-	WAIT_DRQ	= HZ / 10,	/* 100ms */
+	/* spec allows up to 20ms, but CF cards and SSD drives need more */
+	WAIT_DRQ	= 1 * HZ,	/* 1s */
 	/* some laptops are very slow */
 	WAIT_READY	= 5 * HZ,	/* 5s */
 	/* should be less than 3ms (?), if all ATAPI CD is closed at boot */

  reply	other threads:[~2009-12-03  5:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 16:20 Philippe De Muyter
2009-10-27  0:34 ` Robert Hancock
2009-10-27  0:45   ` David Miller
2009-10-27  1:07     ` Robert Hancock
2009-10-27  1:19       ` David Miller
2009-10-27  1:40         ` Robert Hancock
2009-10-27  1:43           ` David Miller
2009-10-27  9:45             ` Philippe De Muyter
2009-10-27 10:24               ` Sergei Shtylyov
2009-10-31 13:56   ` Mark Lord
2009-12-03  5:57     ` David Miller [this message]
2009-12-03  8:55       ` Philippe De Muyter

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=20091202.215738.12118816.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hancockrwd@gmail.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phdm@macqel.be \
    /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®