On Tue, Nov 04, 2014 at 10:01:20AM +0100, Hannes Reinecke wrote: > Hmm. With patch 03/11 and 04/11 you've removed the ordered_tags > fields, on the ground that the block layer never issues ordered tags > nowadays. > Yet these drivers still try to activate ordered tags. > So what's happening here? Broken APIs - in the current tree we can set the ->ordered_tags field through scsi_adjust_queue_depth and scsi_set_tag_type, but that field isn't ever checked except for the queue_type sysfs file and a few pintks. > Do these drivers switch on ordered tags on their own? > If so, why shouldn't the other drivers (like the various FC HBAs) be > allowed to do it, too? > Shouldn't we rather remove ordered tagging from those drivers, too? Except for a few SPI drivers that issue an ordered tag on their own every N commands to avoid locking devices up ordered tag support is gone from the tree (at least on the initiator side). > (Although I'm not too happy about removing ordered tags support in > the other drivers. I have the nagging feeling they might become > important if and when ZBC ever gets off the ground ...) Good luck with that mess. It will have to look very different anyway if it should be remotely supportable, and would be limited to a small set of hardware currently not pretending to have ordered tag support (SAS + SATA basically). -- 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
