On Tue, 2010-11-02 at 07:20 +0900, FUJITA Tomonori wrote: > On Mon, 01 Nov 2010 14:46:56 -0700 > "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx> wrote: > > > On Mon, 2010-11-01 at 21:56 +0900, FUJITA Tomonori wrote: > > > On Sat, 30 Oct 2010 16:05:43 -0700 > > > "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx> wrote: > > > > > > > One final question in that regard is in your ibmvscsis_queuecommand() > > > > code, only INQUIRY, REPORT_LUNS, and MODE_SENSE need to be handled > > > > specially for other non Linux VIO SRP Initiator guests on the other > > > > end.. > > > > > > INQUIRY and REPORT_LUNS need the special responses. Otherwise the > > > initiators can't see the logical units. > > > > > > > There also appears to be a bunch of magic bits set for MODE_SENSE as > > well and seems to indicate a hard requirement for legacy non linux > > guests, yes..? > > No, see ibmvio.c in tgt's user space code. > <nod> > > > Also wrt to the internal REPORT_LUNs emuation, is it just the LUN > > encoding that is specific to ibmvscsis..? I am wondering if can just > > add a operation TCM fabric module TFO op for individual struct > > se_lun->unmapped_lun -> REPORT_LUN payload encode, and drop this > > internal emulation code. > > Yeah. Thanks for the clarification here.. I will look at getting this coded up for TCM core + existing fabric module code and added as a special case for TCM/ibmvscsis. Thanks Tomo-san! --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
