mirrors/scst
1
0
Fork 0
mirror of https://github.com/SCST-project/scst.git synced 2026-05-29 09:50:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Web updates.

Browse Source 
Tooltips code and usage provided by Greg V Zemskov <mne@greg.su> and Kirill Malkin <kirill.malkin@reldata.com>



git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@1412 d57e44dd-8a1f-0410-8b47-8ef2f437770f
This commit is contained in:
Vladislav Bolkhovitin
2009-12-24 13:54:49 +00:00
parent 14fe1bed1e
commit 370a015ad8
10 changed files with 133 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
www/comparison.html
View File

@@ -223,7 +223,8 @@ ORDERED commands</b></td> <td> + </td> <td> + </td> <td> -, <br> data
</b></td> <td> Alpha </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<td align="left"><b>LSI (SAS)</b></td> <td> Preliminary </td> <td> - </td> <td> - </td> <td> - </td>
<td align="left"><b>LSI (SAS)</b></td> <td> Preliminary
(not completed) </td> <td> - </td> <td> - </td> <td> - </td>
</tr>
<tr>
<td align="left"><b>IBM pSeries Virtual SCSI</b></td> <td> - </td> <td> + </td> <td> - </td> <td> - </td>
@@ -278,7 +279,7 @@ CD devices</b></td> <td> - </td> <td> + </td> <td> - </td> <td> - </td>
</tr>
<tr>
<td align="left"><b>Emulation of virtual tape and media changer
devices</b></td> <td> - </td> <td>Experimental</td> <td> - </td> <td> - </td>
devices (VTL)</b></td> <td> - </td> <td>Experimental</td> <td> - </td> <td> - </td>
</tr>
<tr bgcolor="#E0E0E0">

8
www/contributing.html
View File

@@ -49,11 +49,9 @@
<li><span>By reporting bugs or other problems.</span></li>
</ul>
<p>Contributing in SCST, you investing not only
in making Linux <strong>the best storage OS</strong>, but, if your company
has a product or service, based on SCST, you also investing in <strong>the secured
future</strong> of your product or service and, hence, in the <strong>the secured
future</strong> of your company.</p>
<p>Contributing in SCST, you investing not only in making Linux the best storage OS, but, if your company
has a product or service, based on SCST, you also investing in the secured future of your product
or service and, hence, in the the secured future of your company.</p>
<h1>Possible SCST extensions and improvements</h1>

11
www/downloads.html
View File

@@ -36,12 +36,11 @@
<div id="main">
<h1>Stable SCST Releases</h1>
<p>The latest stable version of SCST core is <strong>1.0.1.1</strong>. It requires Linux kernel 2.6.16 or higher.
More detail information you could find in its <strong>README</strong> file.</p>
<p>The latest stable version of SCST core is 1.0.1.1. It requires Linux kernel 2.6.16 or higher.
More detail information you could find in its README file.</p>
<p>The latest development version of <strong>SCST core</strong>, <strong>target drivers</strong> and
<strong>user space utilities</strong> is available directly from the
project's <strong>SVN</strong>. The SCST release policy is to make stable releases once or twice a
<p>The latest development version of SCST core, target drivers and user space utilities is available directly from the
project's SVN. The SCST release policy is to make stable releases once or twice a
year, with the only exception if the current stable version contains a critical bug. But every commit in the
SVN is carefully tested, so you can consider them as mini releases.</p>
@@ -50,6 +49,8 @@
<p><code>svn co https://scst.svn.sourceforge.net/svnroot/scst/trunk</code></p>
<p>Also you can find in the SCST SVN the latest updates for the stable branches.</p>
<p>More information about accessing SVN repository may be found
<a href="http://sourceforge.net/apps/trac/sourceforge/wiki/Subversion">here</a>.</p>

52
www/images/tooltips.js Normal file
View File

@@ -0,0 +1,52 @@
var d = document;
var offsetfromcursorY=15 // y offset of tooltip
var ie=d.all && !window.opera;
var ns6=d.getElementById && !d.all;
var tipobj,op;
function tooltip(el,txt) {
tipobj=d.getElementById('mess');
tipobj.innerHTML = txt;
op = 0.1;
tipobj.style.opacity = op;
tipobj.style.display="block";
tipobj.style.visibility="visible";
el.onmousemove=positiontip;
appear();
}
function hide_info(el) {
d.getElementById('mess').style.visibility='hidden';
d.getElementById('mess').style.display='none';
el.onmousemove='';
}
function ietruebody(){
return (d.compatMode && d.compatMode!="BackCompat")? d.documentElement : d.body
}
function positiontip(e) {
var curX=(ns6)?e.pageX : event.clientX+ietruebody().scrollLeft;
var curY=(ns6)?e.pageY : event.clientY+ietruebody().scrollTop;
var winwidth=ie? ietruebody().clientWidth : window.innerWidth-20
var winheight=ie? ietruebody().clientHeight : window.innerHeight-20
var rightedge=ie? winwidth-event.clientX : winwidth-e.clientX;
var bottomedge=ie? winheight-event.clientY-offsetfromcursorY : winheight-e.clientY-offsetfromcursorY;
if (rightedge < tipobj.offsetWidth) tipobj.style.left=curX-tipobj.offsetWidth+"px";
else tipobj.style.left=curX+"px";
if (bottomedge < tipobj.offsetHeight) tipobj.style.top=curY-tipobj.offsetHeight-offsetfromcursorY+"px"
else tipobj.style.top=curY+offsetfromcursorY+"px";
}
function appear() {
if(op < 0.9) {
op += 0.07;
tipobj.style.opacity = op;
tipobj.style.filter = 'alpha(opacity='+op*100+')';
t = setTimeout('appear()', 30);
}
}

38
www/index.html
View File

@@ -33,7 +33,7 @@
<div id="main">
<h1>Generic SCSI Target Subsystem for Linux</h1>
<p>The <strong>generic SCSI target subsystem for Linux (SCST)</strong> is an alternative
<p>The generic SCSI target subsystem for Linux (SCST) is an alternative
implementation of a SCSI target subsystem for Linux. It provides unified,
consistent interface between SCSI target drivers and
Linux kernel as well as between Linux kernel and storage backend
@@ -63,13 +63,13 @@
<li><span>SCST core undertakes most problems, related to execution contexts, thus practically eliminating one of the most
complicated problem in the kernel drivers development. For example, target drivers for Marvell
SAS adapters or for InfiniBand SRP are less 3000 lines of code long.</span></li>
<li><span>Very low overhead, fine-grained locks and simplest commands processing path allow to reach
maximum possible performance and scalability. Particularly, incoming requests can be processed in
<li><span>Very low overhead and fine-grained locks allow to reach the
maximum performance and scalability. Particularly, incoming requests can be processed in
the caller's context or in one of the internal SCST core's tasklets without any
extra context switches.</span></li>
<li><span>Device handlers, i.e. plugins, architecture allows various I/O
modes in backstorage handling. For example, pass-through device handlers allows to use real
SCSI hardware and vdisk device handler allows to use files as virtual disks.</span></li>
<li><span>Device handlers architecture allows various I/O
modes in backstorage handling. For example, pass-through device handlers allow to export real
SCSI hardware and vdisk device handler allows to export files as virtual disks.</span></li>
<li><span>Advanced per-initiator devices visibility management (LUN masking) allows different
initiators to see different set of devices with different access permissions. For instance,
initiator A could see exported from target T devices X and Y read-writable, and initiator B from
@@ -95,8 +95,7 @@
commands to non-existing devices and provides access control, so different remote
initiators could see different set of devices.</span></li>
<li><span>Other necessary functionality (task attributes, etc.) as specified in SAM-2, SPC-2, SAM-3,
SPC-3 and other SCSI standards.</span></li>
<li><span>Other necessary functionality (task attributes, etc.) as specified in SCSI standards.</span></li>
</ul>
</li>
@@ -110,24 +109,27 @@
will not know about it, which could
lead to various problems, including data corruption. Thus, RESERVE/RELEASE commands, locally generated
UNIT ATTENTIONs, etc. should be intercepted and passed through SCST core.</p>
<p>You can find comparison of SCST with other SCSI targets on the <a href="comparison.html">Comparison</a> page.
Some highlights what it can mean for end users you can find on the <a href="target_iscsi.html">iSCSI-SCST</a> page.
<h1>SCST core supports the following I/O modes</h1>
<ul>
<li><span><strong>Pass-through mode</strong> with one to many relationship, i.e. when multiple initiators can
connect to the exported pass-through devices, for virtually all SCSI devices types: <strong>disks (type 0),
<li><span>Pass-through mode with one to many relationship, i.e. when multiple initiators can
connect to the exported pass-through devices, for virtually all SCSI devices types: disks (type 0),
tapes (type 1), processors (type 3), CDROMs (type 5), MO disks (type 7), medium changers (type 8) and RAID
controllers (type 0xC)</strong>. In this mode you can, for instance, share your parallel SCSI tape or SATA
controllers (type 0xC). In this mode you can, for instance, share your parallel SCSI tape or SATA
DVD-RW device to your iSCSI network.</span></li>
<li><span><strong>FILEIO mode</strong>, which allows to use files on file systems or block devices as virtual
remotely available SCSI disks or CDROMs with benefits of the Linux <strong>cache</strong>.</span></li>
<li><span><strong>BLOCKIO mode</strong>, which performs direct block IO with a block device, bypassing
<li><span>FILEIO mode, which allows to use files on file systems or block devices as virtual
remotely available SCSI disks or CDROMs with benefits of the Linux cache.</span></li>
<li><span>BLOCKIO mode, which performs direct block IO with a block device, bypassing
page-cache for all operations. This mode works well with high-end storage HBAs and for applications that
either do not need caching between application and disk or need the large block throughput.</span></li>
<li><span><strong>User space mode</strong> using scst_user device handler, which allows to implement in the
<li><span>User space mode using scst_user device handler, which allows to implement in the
user space virtual SCSI devices in the SCST environment.</span></li>
<li><span><strong>"Performance" device handlers</strong> as well as <strong>NULLIO</strong> mode provide
<li><span>Performance testing device handlers as well as NULLIO mode to provide
a way for direct performance measurements without overhead of actual data
transferring from/to underlying SCSI device.
transfers from/to underlying SCSI devices.
</span></li>
</ul>
</div>

5
www/scst_admin.html
View File

@@ -57,8 +57,9 @@
<div id="main">
<h1>SCST administration utility</h1>
<p>SCST administration utility <strong>"scstadmin"</strong> developed by Mark Buechler.<br><br>With it you can
manually or automatically using either plain text config file, or MySQL database configure every aspect of SCST.</p>
<p>SCST administration utility scstadmin developed by Mark Buechler.</p>
<p>With it you can manually or automatically using either plain text config file, or MySQL database configure every aspect of SCST.</p>
<p>Especially useful feature of scstadmin is ability to figure out and apply on the currently
running system <strong>changes</strong> in scst.conf file. In other words, you can have SCST subsystem running with configuration from file

2
www/scstvsstgt.html
View File

@@ -44,7 +44,7 @@
<div id="main">
<h1>SCST vs STGT</h1>
<p><strong><a href="http://stgt.berlios.de/">STGT</a></strong> is alternative, independent from SCST implementation
<p><a href="http://stgt.berlios.de/">STGT</a> is alternative, independent from SCST implementation
of SCSI target framework for Linux. It has different architecture, where SCSI target state machine is placed in
the user space, while in SCST all the processing done in the kernel. Such architecture as STGT has was acknowledged
by the Linux SCSI subsystem maintainers as a "right" one, so kernel's part of STGT quickly

71
www/target_iscsi.html
View File

@@ -56,61 +56,62 @@
<div id="main">
<h1>ISCSI target driver iSCSI-SCST</h1>
<p><strong>ISCSI-SCST</strong> is a forked (with all respects) version of IET. Reasons of the fork were:</p>
<p>ISCSI-SCST is an iSCSI target driver for SCST. It is a deeply reworked fork of
<a href="http://iscsitarget.sourceforge.net/">IET</a> with a lot of fixes and improvements. Reasons of the fork were:</p>
<ul>
<li><span>To be able to use full power of <strong>SCST core</strong>.</span></li>
<li><span>To fix all the problems, corner cases issues and iSCSI standard violations IET which has.</span></li>
<li><span>To be able to use full power of SCST core.</span></li>
<li><span>To fix all the problems, corner cases issues and iSCSI standard violations which IET has.</span></li>
</ul>
<p>IET is a well recognized and widely used iSCSI target, but, frankly speaking, it works more or less well
on fast paths and regularly used code branches only, however in many corner
cases it has a lot of problems, like ignoring error processing, as it is for memory allocations,
<p>IET in many corner cases has a lot of problems, like ignoring errors processing, as it is for memory allocations,
crashing itself with BUG() macro, as it is for malformed packets from initiators, possible data
corruptions, because of, for instance, unsafe task management or sessions reinstatement implementations, etc.
There was no way to fix all them without a fork. As the result of this effort nearly 90% of the IET kernel code was fully
rewritten.</p>
<p>Since ISCSI-SCST uses SCST core, it has the following additional features:</p>
There was no way to fix all them without a fork. As the result of this effort nearly all (80-90% overall and >90%
of the core) of the IET kernel code and 20-25% of the user space code were rewritten.</p>
<p>You can find comparison of iSCSI-SCST with IET and other iSCSI targets on the <a href="comparison.html">Comparison</a> page.
Some highlights:
</p>
<ul>
<li><span><strong>Pass-through mode with one to many relationship</strong>, i.e. when multiple initiators can connect to
exported pass-through devices. For instance, in this mode you can safely export your parallel
<strong>SCSI tape</strong> or <strong>tape library</strong> (or <strong>VTL</strong>) on
your iSCSI net and multiple initiators can share it without risk of data loss because of the
shared usage. Existing outdated "rawio" patch for IET supports only non-enforced 1:1
relationship, so it is unsafe to use it in multiple initiators environments.</span></li>
<li><span>Improved performance. In some cases there is >100% improvement.</span></li>
<li><span>Pass-through mode with one to many relationship, when multiple initiators can connect to
exported local SCSI devices. For instance, in this mode you can safely export your parallel
SCSI tape or tape library, or VTL on your iSCSI net and multiple initiators can share it without risk of
data loss because of the shared usage.</span></li>
<li><span><strong>More advanced devices visibility management</strong>, when different initiators can see different set of
devices with different access permissions from the same target.</span></li>
<li><span>Automatic PnP-like reconfiguration, when initiators instantly see any configuration changes on the
target, like addition of new LUNs or a LUN resize. No restart or anything like that is needed.</span></li>
<li><span><strong>O_DIRECT</strong>, i.e. <strong>"BLOCKIO on files"</strong>, mode, which has all advantages
<li><span>Safe implementation of many management and errors recovery facilities as well as better handling of various
corner cases, which means better errors recovery stability without putting user data at risk.</span></li>
<li><span>Advanced devices visibility management, when different initiators can see different set of
devices from the same target.</span></li>
<li><span>O_DIRECT, i.e. "BLOCKIO on files", mode, which has all advantages
of BLOCKIO, but also supports files on file systems. Sometimes, in the appropriate cases,
this mode can make performance difference in 100% or even more.</span></li>
<li><span><strong>4KB blocks</strong> eliminate abysmal write performance caused by misaligned partitions.
<li><span>4KB blocks eliminate abysmal write performance issues caused by misaligned partitions.
</span></li>
<li><span><strong>Virtual CD/DVD-ROMs</strong>.</span></li>
<li><span>Virtual CD/DVD-ROMs.</span></li>
<li><span>Ability to create target devices emulators in the <strong>user space</strong>.</span></li>
<li><span>Ability to create target devices emulators in the user space.</span></li>
<li><span>Ability to create <strong>multi-transport SCSI targets</strong>, which can export (possibly, the same)
devices over multiple transports.</span></li>
</ul>
<p>Also, due to reworked I/O architecture and SCST backend iSCSI-SCST has much
better performance in many cases and has potential for future improvements, like zero-copy
with Linux cache FILEIO. In many tests iSCSI-SCST outperforms tuned for best
performance IET on more than 100%.</p>
<p>Advantages of iSCSI-SCST over IET are summarized on the <a href="comparison.html">Comparison</a> page.</p>
<li><span>Ability to create multi-transport SCSI targets, which can export (possibly, the same)
devices over multiple transports.</span></li>
</ul>
<p>If you are an IET user before installation carefully read README files of both iSCSI-SCST and
the SCST core. Especially pay attention that now the LUN information for iSCSI-SCST is configured not using
iscsi-scstd.conf file in /etc, but using corresponding SCST facilities. This is because now the responsibilities
are divided (as it should be) between the target driver (iSCSI-SCST) and the SCST core: target driver is
responsible for handling targets and their parameters, SCST core is responsible for handling backstorage.</p>
iscsi-scstd.conf file in /etc, but using corresponding SCST facilities. This is because now responsibilities
are divided (as it logically should be) between the target driver (iSCSI-SCST) and the SCSI target core (SCST),
where target driver is responsible for handling targets with their parameters, and SCST core is responsible for handling
backstorage.</p>
<p>The latest stable version is 1.0.1.1. Requires Linux kernel version 2.6.16.x or higher and SCST version 1.0.1.1 or higher.
Tested mostly on i386 and x86_64, but should work on any other supported by Linux platform.</p>

2
www/target_old.html
View File

@@ -75,7 +75,7 @@
download from <a href="http://bj.soulinfo.com/~hugang/scst/tgt/">http://bj.soulinfo.com/~hugang/scst/tgt/</a>.
These drivers are not completed, but looks to be a good starting point if you are going to use one of these adapters.
SCST team don't have the appropriate hardware, therefore have not tested and don't support these drivers.
Send all questions to <strong>Hu Gang < hugang &#64;soulinfo.com ></strong>. If some of these drivers don't compile for
Send all questions to <strong>Hu Gang < hugang at soulinfo com ></strong>. If some of these drivers don't compile for
you, try again with SCST version 0.9.3-pre2.</p><br><br>
<h1>Patches for UNH-iSCSI Target 1.5.03 and 1.6.00 to SCST</h1>

12
www/users.html
View File

@@ -10,6 +10,8 @@
</head>
<body>
<script language="javascript" src="images/tooltips.js" type="text/javascript"></script>
<div id="mess" style="position: absolute; left: 0; top: 0; display: none; padding: 3px; font-size: 13px; font-family: sans-serif; background: #ffffad; color: #26261f; border: 1px solid #909090"></div>
<!-- wrap starts here -->
<div id="wrap">
<div id="header">
@@ -86,17 +88,19 @@
<td class="companybox" width="33%">
<a href="http://www.proxmox.com"><img src="http://www.proxmox.com/cms_proxmox/cms/upload/bilder/temp/pm-test-500.gif" width="275px" alt="Proxmox"></a></td>
<td class="companybox" width="33%">
<a href="http://www.qstar.com"><img src="http://www.qstar.com/templates/qstar/images/qstarweb_template_03.jpg" alt="QStar Technologies"></a></td>
<a href="http://www.reldata.com"><img src="http://www.reldata.com/images/reldata.png" alt="RELDATA" onmouseover="tooltip(this, 'SCST used in FC SAN');" onmouseout="hide_info(this);"></a></td>
</tr>
<tr>
<td class="companybox" width="33%">
<a href="http://www.qstar.com"><img src="http://www.qstar.com/templates/qstar/images/qstarweb_template_03.jpg" alt="QStar Technologies"></a></td>
<td class="companybox" width="33%">
<a href="http://www.scalableinformatics.com"><img src="http://www.scalableinformatics.com/sites/default/files/silogo72.png" alt="Scalable Informatics"></a></td>
<td class="companybox" width="33%">
<a href="http://www.soul.com.cn/"><img src="http://www.soul.com.cn/templates/zh/default/images/logo.gif" alt="Soul Information Technology Co., Ltd."></a></td>
<td class="companybox" width="33%">
<a href="http://www.storwize.com"><img src="http://www.storwize.com/Images/Logo_of.gif" width="275px" alt="Storwize"></a></td>
<a href="http://www.soul.com.cn"><img src="http://www.soul.com.cn/templates/zh/default/images/logo.gif" alt="Soul Information Technology Co., Ltd."></a></td>
</tr>
<tr>
<td class="companybox" width="33%">
<a href="http://www.storwize.com"><img src="http://www.storwize.com/Images/Logo_of.gif" width="275px" alt="Storwize"></a></td>
<td class="companybox" width="33%">
<a href="http://systemfabricworks.com"><img src="http://www.systemfabricworks.com/images/logo.gif" alt="System Fabric Works, Inc."></a></td>
</tr>