lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikYgSrW-fSRNBMU2DWYk2x1xQSAqKhoW1Lijj4N@mail.gmail.com>
Date:	Thu, 2 Sep 2010 15:00:58 -0500
From:	Chris Weiss <cweiss@...il.com>
To:	Vladislav Bolkhovitin <vst@...b.net>
Cc:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	scst-devel <scst-devel@...ts.sourceforge.net>,
	iscsitarget-devel@...ts.sourceforge.net, stgt@...r.kernel.org,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	Mike Christie <michaelc@...wisc.edu>,
	Ross Walker <rswwalker@...il.com>
Subject: Re: [Scst-devel] [ANNOUNCE]: Comparison of features between different
 SCSI targets (SCST, STGT, IET, LIO) updated

On Thu, Sep 2, 2010 at 2:31 PM, Vladislav Bolkhovitin <vst@...b.net> wrote:
> 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.
.
.
>
> If you see I'm wrong somewhere or forgot something, you are welcome to
> correct me and I will fix that.
>
> Vlad
>

as a user following the potential inclusion of a kernel-space target,
iscsi specifically, I would be very interested in seeing what other
pluses the other frameworks have over scst, because if this chart is
accurate, all the other targets have quite a ways to go to catch up.

To me, lacking correct reserve and task management means "not ready
for public consumption".  Making any kernel change that does not have
RESERVE/RELEASE and full TM command support is only going to make
Linux look buggy and amateur-ish in the storage world.  Best to not
change anything than to implement something without them.  These 2
features alone are what helped me choose SCST in the first place.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ