On Wed, 21 Jan 2009 08:45:04 +0100 Henrik Stokseth <henrik@xxxxxxx> wrote: > FUJITA Tomonori wrote: > > > > > > From a quick look at the patch, your driver links requests to a list > > and then the user-space daemon reads the requests via the special > > character device file and sends the response back to kernel space. > > > > If I correctly understand what you want, there are some possible > > alternatives, I guess. > > > > Note that I'm not sure 2) and 3) is acceptable to the SCSI maintainer. > > > > > > 1) use iSCSI initiator and target on the same machine > > > > First, set up iSCSI target software supporting CD/DVD. For example, > > you can use tgt (http://stgt.berlios.de), user-space program. > > > > Then you set up the iSCSI initiator to connect the target. Basically, > > the iSCSI initiator works like a virtual hba as you like. The iSCSI > > initiator and target communicate via tcp while your software > > communicates via the special character device. > > > > If you go with this setup, all you need are already in mainline. > > > > It would be desirable for us to rely upon an interface already present > in the mainstream kernel for practical reasons. > > Pardon the dumb question but is it possible to talk to the TGT framework > without using iSCSI? > > SCST has a nice user-space interface but I couldn't tell whether STGT > had something similar (as documentation is pretty much non-existent). tgt has such but I don't think that anyone needs to use tgt's interface between user and kernel space so there is no documentation (it's better to have such though). tgt user-space daemon supports sbc, ssc, smc, mmc, and osd emulation. Why do you need to invent your own user-space tgt daemon? Why you can't simply use iSCSI? It should work for you. -- 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
