On Wed, 2012-10-24 at 09:25 -0700, K. Y. Srinivasan wrote: > When the low level driver returns SCSI_MLQUEUE_DEVICE_BUSY, > how is the command retried; I suspect the retry is done after some delay. Delay depends mainly on I/O pressure and the unplug timer in the block layer. > Is this delay programmable? If the device state changes, > can the low level driver notify upper layers that it can now handle > the command that it had failed earlier with SCSI_MLQUEUE_DEVICE_BUSY. In theory, you can call blk_run_queue() from the event handler that sees the device become ready. I don't think any driver actually does this, but I can't see it would cause any problem. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
