Eric Youngdale wrote:
> Yes, I am thinking that the interface for selecting queue depths might
> need to be redone so that it is essentially done on a device-by-device
> basis - for the single unit scan case this would work out better anyways.
I agree 100%. I also think there should be a call in for when a device is
removed. More generally though, I don't think this should just be a
select_queue_depths function, more appropriately we simply need a
configure_device() function in the low level driver that gets called with a
device struct, preferably one that includes a complete copy the the INQUIRY
return data, so we can not only set queue depths but also other things like
bus negotiation parameters. I currently have to manually peek into the
INQUIRY data before I pass it back to the mid layer to get this done.
> The only question I have is whether or not there is a circumstance where the
> queue depth is more logically considered to be a bus concept rather than a
> device concept.
Not really, that's why we spec the overall controller queue depth during host
registration time. That should be sufficient for the bus queue depth, and
this should be used for individual device queue depths.
--
Doug Ledford <[EMAIL PROTECTED]> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
