On Fri, 2010-08-20 at 19:43 +0900, FUJITA Tomonori wrote: > On Fri, 20 Aug 2010 03:02:40 -0700 > "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx> wrote: > > > review of TCM core and TCM_Loop. But perhaps at this point LIO-Target > > should go in together with TCM Core and TCM_Loop once mnc can review the > > software iSCSI target pieces..? > > I think that James meant that we have only one scsi target > implementation and we need to replace the current in-kernel target > mode driver. So I don't think that we can merge TCM core without its > ibm vscsi driver. I might be wrong though. Ah yes the ibm vscsi driver. Well for that part I suppose we will need a seperate tcm_ibmvscsi fabric module moving forward. This is where that python script I mentioned when tcm_lpfc, tcm_qla2xxx, tcm_mvsas where originally posted that would generates a new functioning configfs skeleton with NOP I/O path handlers from a handful of user input. Anyways, something like this would really come in handy for making ibm vscsi go, and plus it makes life easier for me too. I will try to get a script along this lines coded up in the next week(s) so that we can finally have a pain-free method of generation for new v4 kernel target mode modules for new developers. There will be no limit per customer. ;) --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
