[9091] in linux-scsi channel archive
Re: Discussion to change SD_TIMEOUT in the sd driver
daemon@ATHENA.MIT.EDU (sjbuller@us.ibm.com)
Wed Jun 28 19:44:29 2000
From: sjbuller@us.ibm.com
To: Doug Ledford <dledford@redhat.com>
Cc: "Boerner, Brian" <Brian_Boerner@ntc.adaptec.com>,
"'linux-scsi@vger.rutgers.edu'" <linux-scsi@vger.rutgers.edu>
Message-ID: <8725690C.0082010C.00@d53mta04h.boulder.ibm.com>
Date: Wed, 28 Jun 2000 17:39:58 -0600
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
"Doug Ledford <dledford@redhat.com>" wrote:
>If you're going to do the work, then make the timeout on a per controller
>basis (I suppose it should actually be on a per device basis when I think
>about it). Maybe add it to the sd disk structs. Then the low level
driver
>can say "Hey, this is a hardware raid logical volume, I'll make it have a
>timeout of 60 seconds" or they can say "this is a passthrough device, 10
>seconds is a plenty long timeout". I for one would take the aic7xxx
driver
>and modify the timeout values back down to about 8 seconds on it's
devices.
>That's more than enough time for any command it sends to complete. Then
the
>hardware raid controller drivers are free to do what they want and they
can
>also timeout logical volumes different from pass through disk devices
>(assuming that they are supported and are treated differently on a
particular
>brand of hardware raid controller).
What about external RAID enclosures attached through the aic7xxx driver?
This would impose an 8 second timeout on them, and they can take
considerably more time if they are in the process of transferring I/O and
cache to the backup controller.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
