When the low level driver returns SCSI_MLQUEUE_DEVICE_BUSY, how is the command retried; I suspect the retry is done after some delay. 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. Regards, K. Y -- 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
