> QUEUE_FULLs happen in bunches. When you have 10 commands waiting to go to a > drive, and you fill its queue, depending on the driver you will either block > the remaining 9 commands or all 10 commands will end up getting sent back to > back and all 10 will QUEUE_FULL out. You want these mass QUEUE_FULL events > to be treated as a single QUEUE_FULL for the purpose of tracking the > device's queue depth. In addition, you want to know the depth the device > was at, not how many commands the mid layer has created. Only the driver > can now that since different drivers queue things differently internally, drivers no longer queue thankfully ;) > there may be commands that are paused and not yet sent to the device but are > present on the card, etc. that'll be hard to find out anyway > command outstanding at a time, any driver that sets cmd_per_lun > 1 must, by > definition, be able to do it's own internal queueing and respect the limit > of 1 command at a time on untagged devices. Hmmmmmmmm are you sure? - : 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
