----- Original Message -----
From: Doug Ledford <[EMAIL PROTECTED]>
To: Eric Youngdale <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; Douglas Gilbert <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, April 12, 2000 2:40 PM
Subject: Re: [PATCH] add-single-device [was: inducing SCSI bus scan]
> 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.
This is quite reasonable too. I can put this on the (long) list of
things I will get to once we start the 2.5 series. We will need a way of
identifying when the device is being added and when it is being removed.
Unless anyone has any better suggestions, a simple boolean parameter would
do for this.
> > 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.
That's what I thought.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
