dev_loss_tmo behavior question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?
--
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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux