On Tue, Jul 27, 2010 at 04:11:48PM -0500, Mike Christie wrote: > Hi FC driver developers, > > I am trying to figure out what is the correct behavior when setting > dev_loss_tmo. > > With lpfc, qla2xx, and ibmfc if I set dev_loss_tmo using > /sys/class/fc_remote_port/rport-xx/dev_loss_tmo, and then we add > devices the slave_configure functions for these drivers reset the > dev_loss_tmo to a driver value. > > The addition of devs could be from something like a user rescan, or > from a scan started by a remote port addition. > > With fcoe, fnic, mptfc, bfa and zfcp the dev_loss_tmo value set from > sysfs will not be reset by a driver value on rescans. > > Which drivers should be changed? At least for zfcp, i don't see a reason for the driver to change the value for dev_loss_tmo. A user could delete the SCSI device at any time from userspace (echo 1 > /sys/.../delete), so the driver has to be able to handle the device removal at any time. And then it should not matter if the removal is triggered from userspace or from the FC transport's dev_loss_tmo. Christof -- To unsubscribe from this list: 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
