On 09/01/05 17:46, Jeff Garzik wrote:
>>>>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_.
>
> It matters quite a bit. One of the main reasons libata uses the SCSI
> layer is for its infrastructure.
Hmm, maybe I should've been more clear.
> This is the same reason a couple RAID drivers use the SCSI layer. It
> has nothing to do with SCSI-as-defined-by-T10, and more to do with the
> fact that SCSI provides a robust queueing/EH/block interface infrastructure.
You must be kidding! "robust"? What are you comparing this to?
I think it's only because "it's there" and that it provides
a uniform access -- provided by SCSI, _not_ by that particular
SCSI implementation.
> My long term plans include moving some of this not-SCSI-related
> infrastructure from the SCSI layer to the block layer.
Which is that infrastructure?
Luben
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
