On Fri, Jul 04, 2014 at 07:21:52PM +0000, Elliott, Robert (Server Storage) wrote: > Perhaps the SCSI midlayer should keep track of both > SCSI target port and logical unit queue depths, parse > the status qualifier if present, and let the host > template advise on the policy to assume if the > status qualifier is not present. We already keep track of the target queue depth, although with the scsi-mq series this is not optional and only done for hosts that declare they have a per-target queue limit by setting ->can_queue in the scsi_target structurue. Only a small number of iSCSI offload HBAs does this. I need to look at the SAM scope defintions, but it doesn't sound too hard to implement. > There is some code for a scsi_target structure that I > don't understand and have just been ignoring: target_busy, > target_blocked, etc. Does that represent the SCSI target > port over multiple logical units, or does that relate to > target-mode where the system is acting as the SCSI target > and presenting logical units itself? It represents the target port, and is not related to target mode support at all. The target mode code uses completely different data structures than the initiator side mid layer. -- 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
