First: what is actually FC specific here? > - timeout handling: > Out of necessity the status of any timed out command is undefined. > So to be absolutely safe HBAs will be using extended timeouts here > (eg 70secs for lpfc). During that time we _could_ signal I/O timeout > to the upper layers, but then the tag will be reused, despite the > HBA still having a reference to it. > I'd like to discuss how this could be solved best with blk-mq. reusing a tag that the hardware hasn't returned is simply unsfafe, nothing really blk-mq specific here. > - Adaption on other HBAs to multiqueue: > The current block-mq design assumes symmetric send and receive > queues (in effect queue pairs). Any hardware _not_ providing this > (like qla2xxx) can not be easily converted to scsi-mq. I'd like to > discuss how one could approach converting these drivers. Why do you think blk-mq assumes this? -- 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
