public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: Ross Biro <ross.biro@gmail.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andre Hedrick <andre@pyxtechnologies.com>
Subject: Re: [PATCH 2/3] WIN_* -> ATA_CMD_* conversion: update WIN_* users to use ATA_CMD_*
Date: Mon, 8 Nov 2004 09:55:48 +0100	[thread overview]
Message-ID: <20041108085545.GI29120@suse.de> (raw)
In-Reply-To: <20041106035522.GA13091@taniwha.stupidest.org>

On Fri, Nov 05 2004, Chris Wedgwood wrote:
> > In particular, most Maxtor and Western Digital Drives will not
> > recover from errors with this command sequence.  The preferred error
> > recovery is to do a reset followed by a set features, because that
> > is what Windows does (as told to me by a drive vendor).
> 
> I assume for Windows they do that for all drives?  Even older ones?
> 
> I also wonder what happens with TCQ when you get an error?  Do you
> just retry everything outstanding?

Any error typically causes an invalidation of the queue, so yes you just
start from scratch. Since PATA doesn't support TCQ anymore, it's not a
worry though :)

-- 
Jens Axboe


  parent reply	other threads:[~2004-11-08  8:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03  9:11 [PATCH] IDE remove some cruft from ide.h Chris Wedgwood
2004-11-05  2:43 ` Jeff Garzik
2004-11-05 13:16   ` Bartlomiej Zolnierkiewicz
2004-11-06  3:22     ` [PATCH 0/3] WIN_* -> ATA_CMD_* conversion: comments Chris Wedgwood
2004-11-06  3:23     ` [PATCH 1/3] WIN_* -> ATA_CMD_* conversion: add new entries to ata.h Chris Wedgwood
2004-11-06 16:48       ` Jeff Garzik
2004-11-06 17:05         ` Jeff Garzik
2004-11-07  6:04           ` [PATCH 0/3] WIN_* -> ATA_CMD_* conversion (take #2): comments Chris Wedgwood
2004-11-07  6:04           ` [PATCH 1/3] WIN_* -> ATA_CMD_* conversion (take #2): add new entries to ata.h Chris Wedgwood
2004-11-08  2:30             ` Jeff Garzik
2004-11-07  6:04           ` [PATCH 2/3] WIN_* -> ATA_CMD_* conversion (take #2): convert users of WIN_* to ATA_CMD_* Chris Wedgwood
2004-11-07  6:04           ` [PATCH 3/3] WIN_* -> ATA_CMD_* conversion (take #2): cleanup hdreg.h Chris Wedgwood
2004-11-06  3:23     ` [PATCH 2/3] WIN_* -> ATA_CMD_* conversion: update WIN_* users to use ATA_CMD_* Chris Wedgwood
2004-11-06  3:45       ` Ross Biro
2004-11-06  3:55         ` Chris Wedgwood
2004-11-06 14:53           ` Ross Biro
2004-11-08  8:55           ` Jens Axboe [this message]
2004-11-06  3:23     ` [PATCH 3/3] WIN_* -> ATA_CMD_* conversion: cleanup hdreg.h Chris Wedgwood

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=20041108085545.GI29120@suse.de \
    --to=axboe@suse.de \
    --cc=andre@pyxtechnologies.com \
    --cc=bzolnier@gmail.com \
    --cc=cw@f00f.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.biro@gmail.com \
    /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