mirrors/scst
1
0
Fork 0
mirror of https://github.com/SCST-project/scst.git synced 2026-05-17 10:41:26 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
7617a7136753ca2d00f52dd67797c2e65bbf1fa6
scst/www/comparison.html
Vladislav Bolkhovitin 1e1476089d Web updates. Particularly, scst_pg has changes suggested by Sam Haxor <generationgnu@yahoo.com> 
git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@858 d57e44dd-8a1f-0410-8b47-8ef2f437770f
2009-05-18 18:08:04 +00:00

438 lines
30 KiB
HTML
Raw Blame History

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta name="Keywords" content="Generic SCSI Target Subsystem for Linux, SCSI targets, iSCSI targets, comparison" />
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta name="author" content="Daniel Fernandes"/>
<meta name="Robots" content="index,follow" />
<link rel="stylesheet" href="images/Orange.css" type="text/css" />
<title>SCSI Targets Comparison</title>
</head>
<body>
<!-- wrap starts here -->
<div id="wrap">
<div id="header">
<div class="logoimg"></div><h1 id="logo"><span class="orange"></span></h1>
<h2 id="slogan">SCSI Target Subsystem for Linux</h2>
</div>
<div id="menu">
<ul>
<li id="sponsorship"><a href="sponsorship.html">Sponsorship</a></li>
<li><a href="index.html">Home</a></li>
<li><a href="http://www.sourceforge.net/projects/scst">Main/News</a></li>
<li><a href="targets.html">Drivers</a></li>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="contributing.html">Contributing</a></li>
<li id="current"><a href="comparison.html">Comparison</a></li>
</ul>
</div>
<!-- content-wrap starts here -->
<div id="content-wrap">
<div id="sidebar">
<h1>Comparison</h1>
<ul class="sidemenu">
<li><a href="comparison.html">Features comparison</a></li>
<li><a href="scstvsstgt.html">SCST vs STGT</a></li>
<li><a href="mc_s.html">MC/S vs MPIO</a></li>
</ul>
</div>
<div id="main">
<h1>Features comparison between Linux SCSI targets</h1>
<p><small>As on April 2009</small></p>
<table bgcolor="#F0F0F0" border="1" cols="5" cellspacing="1" cellpadding="7" style="text-align:center" width="620">
<tr>
<th>
</th><th> <a href="http://scst.sourceforge.net/" title="http://scst.sourceforge.net/" rel="nofollow">SCST</a>
</th><th> <a href="http://stgt.berlios.de/" title="http://stgt.berlios.de/" rel="nofollow">STGT</a>
</th><th> <a href="http://iscsitarget.sourceforge.net/" title="http://iscsitarget.sourceforge.net/" rel="nofollow">IET</a>
</th><th> <a href="http://linux-iscsi.org/" title="http://linux-iscsi.org/" rel="nofollow">LIO</a>
</th></tr>
<tr bgcolor="#E0E0E0">
<td colspan="5"> <b>General</b>
</td></tr>
<tr>
<th align="left"> Upstream kernel</th> <td> - </td> <td> Kernel part </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Generic Target Engine </th> <td> + </td> <td> + </td> <td> iSCSI only </td> <td> Under development </td>
</tr>
<tr>
<th align="left"> Architecture </th> <td> Kernel only</td> <td> User space only
<sup><A HREF="#1">1</A>
</sup> </td> <td> - </td> <td> Kernel only </td>
</tr>
<tr>
<th align="left"> Stability </th> <td> + </td> <td> +
<sup><A HREF="#3">3</A>
</sup> </td> <td> + </td> <td> Heavy development </td>
</tr>
<tr>
<th align="left"> Performance <sup><A HREF="#4">4</A></sup></th> <td> ***** <sup>
<A HREF="#5">5</A>
</sup></td> <td> ***</td> <td> **** </td> <td> ****
<sup><A HREF="#6">6</A></sup></td>
</tr>
<tr>
<th align="left"> Zero-copy passing data between target and
backend drivers</th> <td> + <sup>
<A HREF="#7">7</A>
</sup></td> <td> + <sup>
<A HREF="#8">8</A>
</sup> </td> <td> + </td> <td> + </td>
</tr>
<tr>
<th align="left"> Support for transports without expecting
transfer values (parallel SCSI, SAS) </th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Interface with user space</th> <td> ProcFS </td> <td> Custom </td> <td> - </td> <td> ConfigFS/IOCTL/ProcFS </td>
</tr>
<tr bgcolor="#E0E0E0">
<td colspan="5"> <b>Major features</b>
</td></tr>
<tr>
<th align="left"> Target drivers in kernel space </th> <td> + </td> <td> + </td> <td> - </td> <td> Under development </td>
</tr>
<tr>
<th align="left"> Target drivers in user space </th> <td> + </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Backstorage handlers in kernel space </th> <td> + </td> <td> - </td> <td> - </td> <td> + </td>
</tr>
<tr>
<th align="left"> Backstorage handlers in user space </th> <td> + </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Local access to emulated backstorage devices
<sup><A HREF="#9">9</A></sup></th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Advanced devices access control
<sup><A HREF="#10">10</A></sup></th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Support for Asynchronous Event Notifications
(AEN) </th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Notification for devices added/removed or
resized through AENs or Unit Attentions</th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Bidirectional Commands </th> <td> + <sup>
<A HREF="#11">11</A>
</sup></td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Extended CDB (size >16 bytes) </th> <td> + <sup>
<A HREF="#11">11</A>
</sup></td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Descriptor sense support </th> <td> + </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<th align="left"> RESERVE/RELEASE
<small> (Windows 2003 clustering) </small></th> <td> + </td> <td> + </td> <td> + </td> <td> + </td>
</tr>
<th align="left"> Safe RESERVE/RELEASE implementation according to
SCSI requirements <sup><A HREF="#12">12</A></sup></th> <td> Safe </td> <td> Safe </td> <td> Not safe </td> <td> Not safe </td>
</tr>
<th align="left"> Safe implementation of Task Management commands
<sup><A HREF="#13">13</A></sup></th> <td> Safe </td> <td> Not safe </td> <td> Not safe </td> <td> Not safe </td>
</tr>
<tr>
<th align="left"> Support for SCSI task attributes, including
ORDERED commands</th> <td> + </td> <td> + </td> <td> -, <br/> data
corruption possible
<sup><A HREF="#21">
21</A></sup></td> <td> -, <br/>data
corruption possible
<sup><A HREF="#21">
21</A></sup> </td>
</tr>
<tr>
<th align="left"> Persistent Reservations <br/>
<small> (Windows 2008 clustering)</small></th> <td> - </td> <td> - </td> <td> - </td> <td> Under development </td>
</tr>
<tr>
<th align="left"> ALUA </th> <td> - </td> <td> - </td> <td> - </td> <td> Under development </td>
</tr>
<tr>
<th align="left"> Failover Clustering </th> <td> + </td> <td> ? </td> <td> + </td> <td> + </td>
</tr>
<tr>
<th align="left"> SCSI MIBs </th> <td> - </td> <td> - </td> <td> - </td> <td> -
<sup><A HREF="#15">15</A></sup></td>
</tr>
<tr>
<th align="left"> Cluster Storage Integration </th> <td> - </td> <td> - </td> <td> - </td> <td> VHACS </td>
</tr>
<tr bgcolor="#E0E0E0">
<td colspan="5"> <b>Supported SCSI transports</b>
</td></tr>
<tr>
<th align="left"> iSCSI </th> <td> + </td> <td> + </td> <td> + </td> <td> + </td>
</tr>
<tr>
<th align="left"> Fibre Channel </th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> SRP </th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> iSER </th> <td> - </td> <td> +
<sup><A HREF="#3">3</A>
</sup> </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Parallel (Wide) SCSI </th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> SAS </th> <td> Under
development </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> FCoE </th> <td> Under
development </td> <td>Under
development</<td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> IBM pSeries Virtual SCSI </th> <td> - </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr bgcolor="#E0E0E0">
<td colspan="5"> <b>Supported backstorage</b>
</td></tr>
<tr>
<th align="left"> Kernel side FILEIO </th> <td> + </td> <td> - </td> <td> + </td> <td> + </td>
</tr>
<tr>
<th align="left"> Kernel side BLOCKIO </th> <td> + </td> <td> - </td> <td> + </td> <td> + </td>
</tr>
<tr>
<th align="left"> User space FILEIO </th> <td> + </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> SCSI pass-through
<sup><A HREF="#16">16</A></sup></th> <td> + </td> <td> - </td> <td> - </td> <td> Single initiator only, not enforced
<sup><A HREF="#17">17</A></sup></td>
</tr>
<tr>
<th align="left"> Zero-copy data read/write to/from backstorage</th> <td>BLOCKIO, user space
FILEIO in O_DIRECT mode,
pass-through <sup>
<A HREF="#18">18</A>
</sup></td> <td> - <sup>
<A HREF="#8">8</A>
</sup> </td> <td> BLOCKIO </td> <td> BLOCKIO, pass-
through </td>
</tr>
<tr>
<th align="left"> 4k sectors support in pass-through mode </th> <td> + </td> <td> - </td> <td> - </td> <td> ? </td>
</tr>
<tr>
<th align="left"> 4k, 2k, 1k and 512 byte sectors emulation
in modes, other than pass-through </th> <td> + </td> <td> - </td> <td> - </td> <td> + </td>
</tr>
<tr>
<th align="left"> Virtual CD devices emulation from ISO files </th> <td> + </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Possibility to write to emulated from ISO files
CD devices</th> <td> - </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Emulation of virtual tape and media changer
devices</th> <td> - </td> <td>Experimental</td> <td> - </td> <td> - </td>
</tr>
<tr bgcolor="#E0E0E0">
<td colspan="5"> <b>iSCSI Target</b>
</td></tr>
<tr>
<th align="left"> Architecture </th> <td> Split <sup>
<A HREF="#2">2</A>
</sup> </td> <td> User space
only </td> <td> Split <sup>
<A HREF="#2">2</A>
</sup></td> <td> Kernel only </td>
</tr>
<tr>
<th align="left"> Interface with user space</th> <td>IOCTL/ProcFS/
Netlink</td> <td> - </td> <td>IOCTL/ProcFS/
Netlink</td> <td> ConfigFS/IOCTL/ProcFS </td>
</tr>
<tr>
<th align="left"> Zero-copy data send/receive</th> <td> Send only<sup>
<A HREF="#19">19</A>
</sup> </td> <td> None <sup>
<A HREF="#8">8</A>
</sup> </td> <td> Send only</td> <td> Send only </td>
</tr>
<tr>
<th align="left"><a href="mc_s.html">Multiple connections per session
(MS/C)</a> </th> <td> - </td> <td> - </td> <td> - </td> <td> + </td>
</tr>
<tr>
<th align="left"> Max ErrorRecoveryLevel </th> <td> 0 </td> <td> 0 </td> <td> 0 </td> <td> 2 </td>
</tr>
<tr>
<th align="left"> Bidirectional Commands </th> <td> + <sup>
<A HREF="#11">11</A>
</sup></td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Extended CDB (size >16 bytes) </th> <td> + <sup>
<A HREF="#11">11</A>
</sup></td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<th align="left"> Support for Asynchronous Event Notifications
(AEN) </th> <td> + </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<th align="left"> Safe implementation of connections and sessions
reinstatement <sup><A HREF="#20">20</A></sup></th> <td> Safe </td> <td> Not safe </td> <td> Not safe </td> <td> Not safe </td>
</tr>
<th align="left"> Safe restart <sup><A HREF="#21">21</A></sup></th> <td> Safe </td> <td> ? </td> <td> Not safe </td> <td> ?</td>
</tr>
<tr>
<th align="left"> iSCSI MIBs </th> <td> - </td> <td> - </td> <td> - </td> <td> -
<sup><A HREF="#15">15</A></sup></td>
</tr>
</table>
<br/>
<p><strong><big><u>REMARKS:</u></big></strong></p>
<p><A NAME="1"></A> 1. STGT has SCSI target engine and memory management in user space with small hooks in the kernel to interact with in-kernel target drivers.
As a direct consequence, fully user space STGT target (e.g. iSCSI) can run without any kernel modules needed.</p>
<p><A NAME="2"></A> 2. All iSCSI management implemented in user space and actual data transfers in kernel space without user space involved.</p>
<p><A NAME="3"></A> 3. ISER target driver has long known (since Feb 2008) data corruption problem, which localization hasn't been determined yet and might be
in the STGT core. See <a href="http://lists.berlios.de/pipermail/stgt-devel/2008-February/001367.html">
http://lists.berlios.de/pipermail/stgt-devel/2008-February/001367.html</a> and
<a href="http://lists.wpkg.org/pipermail/stgt/2009-February/002630.html">http://lists.wpkg.org/pipermail/stgt/2009-February/002630.html</a>.</p>
<p><A NAME="4"></A> 4. The result "in average" is listed. One target can be better somewhere, another one somewhere else. Although manual tuning of target and
system parameters tends the restore the difference listed in the comparison. You can find example measurements <a href="vl_res.txt">here</a>,
<a href="bart_res.txt">here</a> and <a href="tomasz_res.txt">here</a>.</p>
<p><A NAME="5"></A> 5. All SCST and its drivers' kernel patches supposed to be applied and SCST with the drivers built in the release or performance build.
Without the kernel patches SCST performance will be at "****+" level, except for the case, when user space backstorage handler used
with iSCSI-SCST iSCSI target driver, where performance will be at "***+" level.</p>
<p><A NAME="6"></A> 6. There is no performance data for LIO, which allow to make a direct comparison with other targets.
The conclusion was made by source code study only. LIO should have performance on the IET level or less,
because of more processing overhead. It might be much less for small block sizes.</p>
<p><A NAME="7"></A> 7. In SCST data are always passed in zero-copy manner between target and backend drivers without need for any
additional kernel patches, except in case, when local access (scst_local) used with user space backend. </p>
<p><A NAME="8"></A> 8. Some zero-copy functionality isn't available from user space, sometimes fundamentally.
For instance, zero-copy FILEIO with page cache or zero-copy send to a socket. Also STGT can't use splice() for in-kernel
target drivers, because it has memory management in user space. To use splice() with socket-based user space target drivers
STGT would need a deep redesign of internal interactions between target drivers, core and backend handlers.</p>
<p><A NAME="9"></A> 9. Local access to emulated backstorage devices" means that you can access emulated by a SCSI target devices
locally on the target host. For instance, you can mount your ISO image from emulated by the target
CDROM device locally on the target host.</p>
<p><A NAME="10"></A> 10. "Advanced devices access control" means that different initiators can see different sets
of devices from the same target. This feature is required for hardware targets, which don't have ability
to create virtual targets.</p>
<p><A NAME="11"></A> 11. Not well tested, because at the moment there is no backend using this functionality.</p>
<p><A NAME="12"></A> 12. SCSI requires that if an initiator clears reservation held by another initiator, the reservation holder must be notified
about the reservation clearance. Otherwise, several initiators can at the same time change supposed to be protected by the
reservation data, which can corrupt them. This is what was called
<a href="http://communities.vmware.com/thread/53797?tstart=0&start=15">"Russian roulette with your data"</a> on the VMware
community forum by someone working for VMware.</p>
<p><A NAME="13"></A> 13. After a task management command completed and before the corresponding response was sent to the initiator, who sent that task management
command, all the affected SCSI commands must get into a state, where they can't affect following after
the tasks management response commands from this initiator. This is the safe implementation.
The unsafe implementation only marks all the affected
SCSI commands as aborted and then immediately send task management response to the initiator. This implementation only
guarantees that the initiator will never receive responses from those commands, but it doesn't
guarantee that none of those commands will get executed by backstorage <strong>*AFTER*</strong> any
SCSI command, which initiator will send after it received the task management response thinking
that all the aborted commands actually fully aborted. This could lead to a data corruption.</p>
<p><A NAME="14"></A> 14. Both IET and LIO report in INQUIRY command response support for full task management model. But they process ORDERED
commands the same way as SIMPLE commands, i.e. allow free reorder of them before they get executed. That violates SCSI standard
and can lead to a data corruption to any application relying on commands order provided by ORDERED attribute.</p>
<p><A NAME="15"></A> 15. The IETF SCSI-MIB (RFC 4455) is not supported by LIO, only proprietary MIBs SBE-SCSI-MIB, SBE-ISCSI-MIB and SBE-IPS-AUTH-MIB are supported.</p>
<p><A NAME="16"></A> 16. SCSI pass-through mode allows to export your local SCSI-capable device. For instance with it you can share your parallel
SCSI tape or SATA DVD-RW device to your iSCSI network.</p>
<p><A NAME="17"></A> 17. LIO doesn't emulate all the necessary SCSI host functionality to allow to share SCSI devices
in pass-through mode to several initiators. It can only pass SCSI commands from initiators to
SCSI devices and responses back. This is safe only with a single initiator. This limitation
isn't enforced anyhow and LIO doesn't issue no warning about it, so you can quietly corrupt your data.
You can find more technical information about that in
<a href="http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg06911.html">
http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg06911.html</a></p>
<p><A NAME="18"></A> 18. You can find proposal how to implement zero-copy FILEIO in SCST on the <a href="contributing.html#ZC_READ">
Contributing</a> page.</p>
<p><A NAME="19"></A> 19. Doesn't need any kernel patch, except in case, when used with user space backend.</p>
<p><A NAME="20"></A> 20. Connections and sessions reinstatement is, basically, a kind of Task Management command, because it implies commands aborting.
For instance, open-iscsi uses it as a less intrusive substistute for target reset in eh_target_reset_handler() callback. So, similarly
to the safe task management above, a safe implementation of connections and sessions reinstatement
must not accept SCSI commands from new connection/session until all the SCSI commands in
being reinstated connection/session get into a state, where they can't affect new commands.</p>
<p><A NAME="21"></A> 21. "Safe restart" means that after the iSCSI target restart, all the connected initiators will seamlessly restore all existing before
the restart connections. "Not safe" means that, most likely, the connected initiators will fail to restore
existing connections with some errors.</p>
<!-- <p><small><strong>P.S.</strong> You can find a brief background history of this comparison page <a href="comparison_history.html">here</a>.</small></p> -->
</div>
</div>
</div>
<!-- wrap ends here -->
<!-- footer starts here -->
<div id="footer">
<p>
&copy; Copyright 2008-2009 <b><font color="#EC981F">Vladislav Bolkhovitin & others.</font>&nbsp;&nbsp;
Design by: <b><font color="#EC981F">Daniel Fernandes</font></b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</p>
</div>
<!-- footer ends here -->
</body>
<!-- Piwik -->
<script type="text/javascript">
var pkBaseURL = (("https:" == document.location.protocol) ? "https://apps.sourceforge.net/piwik/scst/" : "http://apps.sourceforge.net/piwik/scst/");
document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
</script><script type="text/javascript">
piwik_action_name = '';
piwik_idsite = 1;
piwik_url = pkBaseURL + "piwik.php";
piwik_log(piwik_action_name, piwik_idsite, piwik_url);
</script>
<object><noscript><p><img src="http://apps.sourceforge.net/piwik/scst/piwik.php?idsite=1" alt="piwik"/></p></noscript></object>
<!-- End Piwik Tag -->
</html>
Reference in New Issue View Git Blame Copy Permalink