linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@redhat.com>, Tejun Heo <htejun@gmail.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: PIO with SSDs: needs a long DRQ-after-command timeout for WRITEs
Date: Tue, 30 Dec 2008 08:53:39 -0500	[thread overview]
Message-ID: <495A27E3.50801@rtr.ca> (raw)

Guys,

I'm still lurking around in the shadows here, but something just
came to light on another project which might affect mainline.

We're using new, cheap 32GB Transcend MLC SSDs with a PATA interface.
Normally, folks would use UDMA with these, and never notice an issue.

But this project has only (very slow) PIO interfaces, and the SSDs
didn't work at first on the old kernel here.

The fix, was to increase the allowed amount of time for the drive
to assert DRQ after s/w issues a PIO WRITE to the drive.

The kernel I was using here had a 50msec timeout (ATA spec requires
at least 20msec), but this was insufficient for these SSDs.

I suspect the SSDs perform an ERASE operation on WRITE,
before asserting DRQ, and this takes a bit of time.

Not sure how much time, but we just bumped the timeout up
to a few seconds and all is working again.  Overkill, yes.

So.. how long does libata and current IDE allow for initial DRQ assertion?
It should probably be at least 500msec or more now.

Cheers

             reply	other threads:[~2008-12-30 13:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 13:53 Mark Lord [this message]
2008-12-30 13:59 ` PIO with SSDs: needs a long DRQ-after-command timeout for WRITEs Alan Cox
2008-12-31 16:29   ` Mark Lord
2008-12-31 18:38     ` Bartlomiej Zolnierkiewicz
2008-12-31 20:30       ` Mark Lord
2008-12-30 18:14 ` Robert Hancock
     [not found]   ` <495B9D31.6080904@rtr.ca>
2008-12-31 17:33     ` Robert Hancock
2008-12-31 18:03       ` Sergei Shtylyov
2008-12-31 18:06       ` Sergei Shtylyov

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=495A27E3.50801@rtr.ca \
    --to=liml@rtr.ca \
    --cc=alan@redhat.com \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --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).