All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: stgt-devel@lists.berlios.de
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	dougg@torque.net, scst-devel <scst-devel@lists.sourceforge.net>,
	linux-scsi@vger.kernel.org
Subject: Re: [Stgt-devel] Question for pass-through target design
Date: Fri, 01 Jun 2007 19:12:01 +0400	[thread overview]
Message-ID: <46603741.308@vlnb.net> (raw)
In-Reply-To: <463F36AC.3010207@vlnb.net>

Vladislav Bolkhovitin wrote:
> So, if you need in-kernel pass-through I would suggest you to look at
> SCST project (http://scst.sf.net), which is currently stable and mature,
> although also not fully finished yet. It was historically from the very
> beginning designed for full feature in-kernel pass-through for not only
> stateless SCSI devices, like disks, but also for stateful SCSI devices
> (like SSC ones a.k.a. tapes), where the correct handling of all above is
> essential. In additional to considerably better performance, the
> complete in-kernel approach makes the code simpler, smaller and cleaner
> as well as allows such things as zero-copy buffered file IO, i.e. when 
> data are sent to remote initiators or received from them directly 
> from/to the page cache (currently under development). For those who need 
> implementing SCSI devices in the user space scst_user module is about to 
> be added. Since the SCSI state machine is in kernel the interface 
> provided by scst_user is very simple, it essentially consists from only 
> a single IOCTL and allows to have overhead as low as a single syscall 
> per SCSI command without any additional context switches. It is already 
> implemented and works. For some legal reasons I can't at the moment 
> publish it, but you can see its full description in the project's SVN 
> docs (you can get them using command "svn co 
> https://svn.sourceforge.net/svnroot/scst/trunk/doc").

Now I released scst_user module and it is available from the SCST SVN, 
so you can check how simply it allows to write SCSI devices, like a VTL, 
in the user space.

Vlad

      parent reply	other threads:[~2007-06-01 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070504160712.GB16528@austin.ibm.com>
     [not found] ` <200705041704.l44H4WXa003789@mbox.iij4u.or.jp>
     [not found]   ` <463B72F6.3000207@torque.net>
     [not found]     ` <20070506053629P.fujita.tomonori@lab.ntt.co.jp>
2007-05-07 14:24       ` [Stgt-devel] Question for pass-through target design Vladislav Bolkhovitin
2007-05-07 15:10         ` FUJITA Tomonori
2007-05-07 15:27           ` Vladislav Bolkhovitin
2007-05-07 15:37             ` FUJITA Tomonori
2007-05-07 16:52               ` Vladislav Bolkhovitin
2007-05-08  5:51                 ` Vladislav Bolkhovitin
2007-05-22 19:56           ` Robert Jennings
2007-05-23 10:45             ` Vladislav Bolkhovitin
2007-05-24 19:01               ` Robert Jennings
2007-05-25 14:38                 ` Vladislav Bolkhovitin
2007-06-01 15:12         ` Vladislav Bolkhovitin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46603741.308@vlnb.net \
    --to=vst@vlnb.net \
    --cc=dougg@torque.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    --cc=stgt-devel@lists.berlios.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.