linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>,
	ltuikov@yahoo.com, Albert Lee <albertcc@tw.ibm.com>,
	linux-ide@vger.kernel.org,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Doug Maxey <dwm@maxeymade.com>
Subject: Re: [RFC] libata new EH document
Date: Thu, 01 Sep 2005 17:40:44 -0400	[thread overview]
Message-ID: <4317755C.5080700@adaptec.com> (raw)
In-Reply-To: <1125581097.4834.5.camel@mulgrave>

On 09/01/05 09:24, James Bottomley wrote:
> On Thu, 2005-09-01 at 01:54 -0400, Jeff Garzik wrote:
> 
>>The long term direction for the SCSI core seems to be that of
>>requiring auto-sensing.
> 
> 
> No, I don't see the mid-layer error thread handling of this ever going
> away.
> 
>>libata is simply being lazy:  while the SCSI core continues to support
>>kicking the EH thread when sense is missing, it's preferred for libata
>>to reuse that infrastructure.
> 
> 
> That makes the most sense ;-)

For libata it doesn't really matter, since it is _ATA_.

> The current SCSI autosense in drivers doesn't require this because we
> reuse the existing command that got the contingent allegiance condition.

Care to elaborate what "contingent allegiance condition" is,
how SCSI Core got it, how SCSI Core is using it, and how SCSI Core set
it up with the LU?

> This is the piece I'd like to get rid of because the extra fields and
> extra setup to allow the command to be reused are a critical path hit.

If you _do_ get rid of the extra fields, then you _really_ need
LLDD/protocols to support autosense.

> If you look at any driver that does this (53c700.c for instance) you'll
> see that the command is turned around and resubmitted in the irq
> routine).

That's ok.

	Luben

  reply	other threads:[~2005-09-01 21:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29  6:11 [RFC] libata new EH document Tejun Heo
2005-08-29  6:13 ` Tejun Heo
2005-08-30  9:10 ` Albert Lee
2005-08-30 10:26   ` Tejun Heo
2005-08-30 14:32     ` Luben Tuikov
2005-09-01  1:17       ` Tejun Heo
2005-09-01  2:22         ` Jeff Garzik
2005-09-01  2:42           ` Tejun Heo
2005-09-01  3:33           ` Luben Tuikov
2005-09-01  3:30         ` Luben Tuikov
2005-09-01  3:44           ` Tejun Heo
2005-09-01  4:38             ` Luben Tuikov
2005-09-01  5:44               ` Tejun Heo
2005-09-01  5:54                 ` Jeff Garzik
2005-09-01 13:24                   ` James Bottomley
2005-09-01 21:40                     ` Luben Tuikov [this message]
2005-09-01 21:46                       ` Jeff Garzik
2005-09-01 22:09                         ` Luben Tuikov
2005-09-01 22:27                           ` Jeff Garzik
2005-09-01 23:17                             ` Luben Tuikov
2005-09-02  7:09                             ` Stefan Richter
2005-09-01 22:22                         ` Luben Tuikov
2005-09-01 22:31                           ` Jeff Garzik
2005-09-01 21:55                       ` James Bottomley
2005-09-01 22:07                         ` Luben Tuikov
2005-09-01 22:23                           ` James Bottomley
2005-09-01 22:36                             ` Luben Tuikov
2005-09-01 23:01                               ` James Bottomley
2005-09-01 23:03                                 ` Luben Tuikov
2005-09-01 23:27                                 ` Luben Tuikov
2005-09-01  2:22     ` Jeff Garzik
2005-08-30 14:27   ` James Bottomley
2005-09-07  8:25 ` Jeff Garzik

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=4317755C.5080700@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=albertcc@tw.ibm.com \
    --cc=dwm@maxeymade.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ltuikov@yahoo.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;
as well as URLs for NNTP newsgroup(s).