On Sunday December 18, 2011 Nicholas Bellinger wrote: > So to get the ball rolling on remaining items, one question is still how to > resolve mixed target/initiator mode operation on a HW per port context basis..? > > This is currently done with a qla2xxx module parameter, but to do mixed mode > properly we will need something smarter between scsi-core and target-core ports. > Note we currently set qlini_mode = QLA2XXX_INI_MODE_STR_DISABLED, so by default > patch #1 will effectively disable initiator mode by skipping scsi_scan_host() > from being called in to avoid scsi-core timeouts when performing immediate > transition from initiator mode -> target mode via ISP reset. > > What we would like to eventually do is run qla2xxx LLD to allow both initiator > and target mode access based on the physical HW port. We tried some simple > qla_target.c changes this make this work, but to really do it properly > and address current qlini_mode = QLA2XXX_INI_MODE_STR_DISABLED usage it will > need to involve scsi-core so that individual HW port can be configured and > dynamically changed across different access modes. (sorry for the late reply) Dynamically switching between initiator mode, target mode or even using both modes simultaneously is already possible for iSCSI over Ethernet and for SRP over InfiniBand with the current SCSI core. Why would the SCSI core have to be modified in order to make the same possible for FCP ? Am I missing something ? If SCSI initiator timeouts during initiator-to-target mode transitions are an issue, why not to abort pending SCSI commands before performing the transition ? Bart. -- 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
