need help to merge (small) virtual scsi driver upstream.

[aboobacker vadakkumuri valappil]

Good... Well, i am not sure about your commend about iSCSI. There has not
been any transport protocols, which is as feature rich and robus as iSCSI :)
It is the industry standard for SCSI transport. The other expensive option
is fibrechannel. iSCSI has been bread and butter for a lot of storage
companies these days.

BTW, i see you using the copy_to_user, have you thought about using netlink
sockets or memory mapping techniques to transfer data between user space and
kernel?

Aboo



2009/1/20 Matt Mackall <mpm at selenic.com>

> On Tue, 2009-01-20 at 08:52 +1100, aboobacker vadakkumuri valappil
> wrote:
> > Anyway, on another note, i also had similar project. Have a look at
> > this http://vscsihba.aboo.org/ also. This was my project few years
> > ago.  My poject was not just to prsent the file as a disk, but to ship
> > the SCSI commands off the kernel to user space, and a user API could
> > be used to develop any SCSI transport techniqies in user space. Your
> > driver seems to have the same method.
>
> We've got something very similar to this in the kernel already and it's
> called iSCSI. iSCSI is a moderately straightforward encapsulation of the
> SCSI protocol in TCP. It's not great, but at least it's standardized.
>
> If you have code that generates SCSI packets in userspace, it's
> relatively straightforward to convert those to iSCSI packets and serve
> them over TCP and then attach to your virtual SCSI device from the
> kernel. And yes, this even works with things other than disks.
>
> --
> http://selenic.com : development and support for Mercurial and Linux
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/kernel-mentors/attachments/20090120/6e08adba/attachment.htm