> ok fair enough... what kind of granularity can this delay be set too? > It might make sense to default to say 50 usec or 100usec always... Range is in milliseconds, and capped to a value < 100ms. We had the same thoughts. In general we concluded that the lost cycles in queuecommand probably still outweighs the gain. This, coupled with the general hesitancy to change the base behavior w/o a compelling reason, (and the qual impacts) means we have no desire to change the default. > Also, not sure how your hardware works but it would be really sweet if > the kernel could set "this request should be coalesed" or > "this request > is latency sensitive, gimme immediate", so that we can set async write > IO's for coalescing while not getting latency on reads... Yep. Unfortunately, nothing this granular. -- james - : 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
