public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	scst-devel <scst-devel@lists.sourceforge.net>,
	iscsitarget-devel@lists.sourceforge.net, stgt@vger.kernel.org
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	Mike Christie <michaelc@cs.wisc.edu>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Ross Walker <rswwalker@gmail.com>
Subject: [ANNOUNCE]: Comparison of features between different SCSI targets (SCST, STGT, IET, LIO) updated
Date: Thu, 02 Sep 2010 23:31:17 +0400	[thread overview]
Message-ID: <4C7FFB85.7000006@vlnb.net> (raw)

Hello,

I updated the Linux SCSI targets comparison page 
http://scst.sourceforge.net/comparison.html, which compares features of 
the existing Linux SCSI target subsystems. The comparison includes SCST, 
STGT, IET and LIO. I added IET there, because it is the most used Linux 
iSCSI target at the moment.

This page is intended to be a complete and fair feature-by-feature 
comparison between the targets. The only thing I have not added there is 
quality of various corner cases recovery, because I don't know how to 
measure that. SCST is really good in this area, while some other targets 
are often not too much, but I have no idea how to summarize it in an 
objective view.

If you see I'm wrong somewhere or forgot something, you are welcome to 
correct me and I will fix that.

Vlad



             reply	other threads:[~2010-09-02 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 19:31 Vladislav Bolkhovitin [this message]
2010-09-02 20:00 ` [Scst-devel] [ANNOUNCE]: Comparison of features between different SCSI targets (SCST, STGT, IET, LIO) updated Chris Weiss
2010-09-02 20:12   ` Nicholas A. Bellinger
2010-09-02 20:50     ` Chris Weiss
2010-09-02 21:31       ` Nicholas A. Bellinger
2010-09-06 21:51     ` Vladislav Bolkhovitin

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=4C7FFB85.7000006@vlnb.net \
    --to=vst@vlnb.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=iscsitarget-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=nab@linux-iscsi.org \
    --cc=rswwalker@gmail.com \
    --cc=scst-devel@lists.sourceforge.net \
    --cc=stgt@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox