mirrors/scst
1
0
Fork 0
mirror of https://github.com/SCST-project/scst.git synced 2026-08-18 05:06:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

Web updates

Browse Source 
git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@1006 d57e44dd-8a1f-0410-8b47-8ef2f437770f
This commit is contained in:
Vladislav Bolkhovitin
2009-08-04 11:10:18 +00:00
parent 70110ec078
commit 24f4743f68
2 changed files with 7 additions and 131 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/comparison.html
+7 -5
View File
@@ -43,7 +43,7 @@
<div id="main">
<h1>Features comparison between Linux SCSI targets</h1>
<p><small>As on July 2009</small></p>
<p><small>As on August 2009</small></p>
<table bgcolor="#F0F0F0" border="1" cols="5" cellspacing="1" cellpadding="7" style="text-align:center" width="620">
@@ -164,10 +164,14 @@ ORDERED commands</th> <td> + </td> <td> + </td> <td> -, <br/> data
</tr>
<tr>
<th align="left"> Persistent Reservations <br/>
<small> (Windows 2008 clustering)</small></th> <td> - </td> <td> - </td> <td> - </td> <td> Under development </td>
<small> (Windows 2008 clustering / RHEL5 I/O fencing)</small></th> <td> Under development,
patch is <a href=
"http://sourceforge.net/mailarchive/forum.php?thread_name=4A72ECF1.2090906%40vlnb.net&forum_name=scst-devel">
available</a> for
testing</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>
<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>
@@ -417,8 +421,6 @@ reinstatement <sup><A HREF="#21">21</A></sup></th> <td> Safe </td> <td> Not s
existing connections with some errors. However, your iSCSI initiator also should be able to handle the safe restart. For instance,
old (pre-CentOS/RHEL 5) open-iscsi has problems in this area. But the latest versions do it pretty well.</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>
www/comparison_history.html
-126
View File
@@ -1,126 +0,0 @@
<!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" />
<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 History</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>Generic SCSI Target Subsystem for Linux</h2>
</div>
<div id="menu">
<ul>
<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">
<h3>Some background history of the <a href="comparison.html">Features comparison</a> page.</h3>
<p>LIO was the first who has had similar comparison
<script type="text/javascript">
document.write("<a href=\"ht");
document.write("tp://www.linux-is");
document.write("csi.org/index.php/Main_Page#Feature_Overview\">page<\/a>");
</script>
<noscript>page http://www.linux-iscsi.org/index.php/Main_Page</noscript>. It was and still is very much
wrong about SCST. I asked that page author, Nicholas Bellinger, to
correct the wrong items (see <a href="http://sourceforge.net/mailarchive/forum.php?thread_name=49AECE0B.5030009%40vlnb.net&forum_name=scst-devel">my
e-mail</a>), but Nicholas Bellinger refused to do it without any explanations. Moreover, he
blocked my access to the LIO mailing list, preventing me from telling that
to the interested people myself. After all our previous discussions and
with his skills and experience it's nearly impossible to believe that Nicholas Bellinger
didn't know that SCST is a lot more generic than LIO and has zero-copy
in all the same places, where LIO has. Thus, that comparison page is looking like rather a deliberate cheating
attempt. Seems SCST is so much superior over LIO, so Nicholas Bellinger gave up technical discussions and started
attacking people's perception about SCST, trying to inspire them the opposite.</p>
<h4>Update</h4>
<p>After our comparison page was published, Nicholas Bellinger corrected in his comparison page the most crying items about SCST. Namely:
he acknowledged that SCST is a generic engine as well as marked "zero-copy" item for SCST as "Needs kernel patch" and removed "User Interface" item.
But "zero-copy" mark for SCST is still wrong, because
SCST needs kernel patch to provide send zero-copy in the iSCSI target driver (and only in it) only if it is working with user space backend. LIO doesn't
support user space backend, so, if it has "X" in this line, SCST must also have unconditional "X" there.</p>
<p>Moreover, new wrong items where introduced:
<ul>
<li><span>SCST was marked as "-" in "Additional Header Segment" and "Bidirectional Commands" items.
SCST and iSCSI-SCST support bidirectional commands as well as iSCSI-SCST supports other values in the
Additional Header Segment (namely, extended CDB).</span></li>
<li><span>STGT marked as having Fibre Channel target drivers for Emulex, QLogic and LSI adapters. Where are they?</span></li>
<li><span>STGT marked as having Fibre Channel QLogic target driver in-tree. Which tree is meant?</span></li>
<li><span>STGT marked as supporting SAS and parallel SCSI targets. But
it fundamentally can't do that. Those transports don't provide expecting
transfers values (size and direction), so those values must be extracted
directly from CDBs. STGT doesn't have the necessary infrastructure for that, see, for instance,
<a href="https://lists.berlios.de/pipermail/stgt-devel/2007-March/000436.html">"https://lists.berlios.de/pipermail/stgt-devel/2007-March/000436.html</a>.
Nothing has changed since time, when that e-mail was sent.
</ul>
<p>Interesting coincidence that the above wrong STGT items were added at nearly the same time as LIO started working with STGT's in-kernel target drivers...</p>
</p>
</div>
</div>
</div>
<!-- wrap ends here -->␍
<!-- footer starts here -->
<div id="footer">
<p>
&copy; Copyright 2004-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>