Steve Byan wrote:
On Mar 2, 2006, at 11:21 AM, Vladislav Bolkhovitin wrote:
Could anyone advice how a SCSI target device can IO-throttle its
initiators, i.e. prevent them from queuing too many commands, please?
I suppose, the best way for doing this is to inform the initiators
about the maximum queue depth X of the target device,
[...]
Returning QUEUE FULL status is correct, unless the initiator does not
have any pending commands on the LUN, in which case you should return
BUSY. Yes, this can lead to out-of-order execution. That's why tapes
have traditionally not used SCSI command queuing.
Look into the unit attention interlock feature added to SCSI as a
result of uncovering this issue during the development of the iSCSI
standard.
Apparently, hardware SCSI targets don't suffer from queuing overflow
[...]
No, they just have big queues.
Depending on the the transport protocol, the problem of queue depth at
the target may not even exist in the first place. This is the case with
SBP-2 where the queue of command blocks resides at the initiator.
--
Stefan Richter
-=====-=-==- --== ---==
http://arcgraph.de/sr/
-
: 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
