On Mon, 2012-03-19 at 08:54 +0000, James Bottomley wrote: > On Sun, 2012-03-18 at 17:22 -0700, Nicholas A. Bellinger wrote: > > On Sun, 2012-03-18 at 09:22 +0000, James Bottomley wrote: > > > On Fri, 2012-03-16 at 16:40 -0700, Nicholas A. Bellinger wrote: > > > > James & Co, > > > > > > > > Ping..? Any thoughts on this topic yet..? > > > > > > Not really ... we're trying to get the participants to plan the topics > > > this year. > > > > > > > Hi James, > > > > I'm asking because the invites for an LSF slot this year to discuss this > > topic with the development community has not materialized, and you've > > been completely silent to qla2xxx target RFCs + patches that involve the > > subject thus far.. > > It's not my driver, it's qlogic's ... I'm not really going to say > anything until they do. Well, I think most of the questions unresolved around mixed mode that need to be addressed between scsi-core and target-core for-3.5 are really quite generic in nature to the individual scsi LLD. Currently where we run into difficultly with a storage stack that is made to allow 'hot' transition between different modes of operation, is how to relinquish initiator mode operation w/o having to unload the whole SCSI LLD, and also how to re-enable initiator mode when an individual TCM fabric port have been released by a generic wwn_group object under /sys/kernel/config/target/$FABRIC/$FABRIC_WWPN So considering these current limitations here between subsystems for the initial for-3.4 merge of qla_target.c logic, we now enforce the use of a qla2xxx specific module parameter to enable/disable different modes globally for all qla_hw_data ports at LLD load time. I've asked Andrew V. and Co. to take another look at today's linux-next tree to verify the changes for existing code in patch #2 for >= qla24xx series target mode support do not negatively effect the existing initiator mode operation of qla2xxx in any way. Please let us know if you have any concerns. Thanks, --nab -- 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
