----- Original Message -----
From: "Douglas Gilbert" <[EMAIL PROTECTED]>
To: "Ricky Beam" <[EMAIL PROTECTED]>
Cc: "Stanley Wu" <[EMAIL PROTECTED]>; "Linux SCSI list"
<[EMAIL PROTECTED]>
Sent: Wednesday, June 14, 2000 11:34 PM
Subject: Re: Can we change the SCSI command timeout?
> I tried to add some logic to the mid level driver [core] so that the
> upper level drivers (specifically sg under superuser's instruction)
> could request a SCSI bus/device/host reset. Basically the patch was
> rejected because it might interfere with the mid level's error
> processing.
I thought we worked through all of those issues. I thought we were
going to add a hook
to let the error handling thread perform the reset - this would take care of
the synchronization
with any other devices on the bus that might be active at the time.
> My feeling is that in some contexts [best known to a user application
> or an upper level driver] turning off the mid level's error processing
> might be advantageous. There is also no way for an application or an
> upper level driver to abort a SCSI command in progress. This means
> that an application can't set an extremely long timeout to the SCSI
> subsystem, run its own timer, and if that timer expires, abort the
> outstanding command.
The context would also be only known to the administrator who is
attempting
to use the feature. Even if the bus is temporarily idle, a bus reset can
change state for a device
(i.e. cause a tape drive to retension), so you really have to pay attention
to what you are doing.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
