On 09/29/2009 08:34 PM, Giridhar Malavali wrote:
3) From your previous mail, I understand that you don't require a
combined limit per target. Say the total queue depth for all LUN's on a
particular target should not exceed some threshold.
James Smart had done this patch
http://marc.info/?l=linux-scsi&m=121070114018354&w=2
where it sets the starget->can_queue based on info we get from vendors.
The patch did not get merged. JamesB does not want the
starget->can_queue to be static, and wants code like the queue full
tracking code which dynamically ramps the device queue depth up and down.
I am not sure if JamesB meant that he wants to ramp down the
starget->can_queue based on getting a QEUEU_FULL though. I thought he
just meant he wants it to be dynamic. If I am right, then I think we
could use JamesS's patch to set an initial starget->can_queue and add
another field for a max value. Then we could add some code that ramps
down/up based on something like command completion time or throughput or
some other value.
If JamesS did mean that he wanted to ramp down the starget->can_queue
based on QUEUE_FULLs then JamesS and JamesB do not agree on that and we
are stuck.
--
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
