On Thu, 2014-01-16 at 11:59 -0500, Alan Stern wrote:
> Since the START-STOP and TEST UNIT READY (or REQUEST SENSE or
> whatever)
> commands are likely to take a long time, they should all be carried
> out
> asynchronously with respect to the resume procedure. I don't know
> what
> the best way is to implement this. But it is important to guarantee
> that in the RPM_ACTIVE case, the START-STOP command gets sent to the
> disk before any other commands. (This isn't an issue in the
> RPM_SUSPENDED case, as the block layer will prevent requests being
> sent out unless they have the REQ_PM flag set.)
>
> Does this plan sound reasonable to everyone? Are there important
> aspects I haven't considered (such as interactions between the SCSI
> and
> ATA layers)?
The START-STOP may result in an error. What do you do in that case?
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
