From: stansmith <stansmith@ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86>
Date: Tue, 29 Dec 2009 21:31:52 +0000 (+0000)
Subject: [DOCS] manual.htm - Corrected uDAT/uDAPL discussion as uDAPL v1.1 provider is no... 
X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=6362c96e60a8c29d00ce4d6995212249bcbe07ba;p=~shefty%2Frdma-win.git

[DOCS] manual.htm - Corrected uDAT/uDAPL discussion as uDAPL v1.1 provider is no longer supported. Fixed lingering %ProgramFiles(x86)% install path problems; removed (x86) as WinOF is installed as %ProgramFIles%\ on all systems. Updated SRP discussion to include a how to configure a Linx/OFED SRP target (vdisk+BLOCKIO) accessible from Windows.

git-svn-id: svn://openib.tc.cornell.edu/gen1@2646 ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86
---

diff --git a/branches/WOF2-2/docs/Manual.htm b/branches/WOF2-2/docs/Manual.htm
index d9562227..0498658c 100644
--- a/branches/WOF2-2/docs/Manual.htm
+++ b/branches/WOF2-2/docs/Manual.htm
@@ -13,9 +13,9 @@ div.Section1
 <a href="#TOP"></a> </h1>
 <h1 align="center">Windows OpenFabrics </h1>
 <h1 align="center">User's Manual</h1>
-<h2 align="center">Release 2.1</h2>
+<h2 align="center">Release 2.2</h2>
 <h3 align="center">
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->12/10/2009<!--webbot bot="Timestamp" endspan i-checksum="12507" --></h3>
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->12/29/2009<!--webbot bot="Timestamp" endspan i-checksum="12659" --></h3>
 <h2 align="left"><u>Overview</u></h2>
 <p align="left"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'">
 The Windows OpenFabrics (WinOF) package is composed of software modules intended 
@@ -90,7 +90,7 @@ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none;
 	<br>&nbsp;</li>
 </ul></li>
 	<li>
-	<h3 align="left"><a href="#SRP">SRP (SCSI RDMA) Protocol Driver</a></h3></li>
+	<h3 align="left"><a href="#SRP">SRP (SCSI over RDMA) Protocol Driver</a></h3></li>
 	<li>
 	<h3 align="left"><u><font color="#0000FF"><a href="#QLOGICVNIC">QLogic VNIC_Driver</a></font></u></h3></li>
 	<li>
@@ -4066,13 +4066,15 @@ order provide a set of transport-independent, platform-independent Application
 Programming Interfaces that exploit the RDMA (remote direct memory access) 
 capabilities of next-generation interconnect technologies such as InfiniBand, 
 and iWARP.</font></p>
-<p align="left"><font face="Times New Roman">WinOF DAT and DAPL are based on the 1.1 DAT specification. The DAPL 
+<p align="left"><font face="Times New Roman">WinOF uDAT and uDAPL are based on the 
+2.0 DAT specification. The DAPL 
 (Direct Access Provider Library) which now fully supports Infiniband RDMA and 
 IPoIB.</font></p>
-<p align="left"><font face="Times New Roman">WinOF 1.0.1, and future WinOF 
-releases, will include DAT/DAPL version 2.0 runtime libraries along with an optional 
-v2.0 application build environment.<br>
-DAT 2.0 is configured with InfiniBand extensions enabled. The IB extensions 
+<p align="left"><font face="Times New Roman">Previous WinOF 
+releases supported the uDAT/uDAPL 1.1 provider which has now been deprecated.<br>
+uDAT/uDAPL version 2.0 runtime libraries along with an optional 
+v2.0 application build environment are the only options.<br>
+uDAT 2.0 is configured with InfiniBand extensions enabled. The IB extensions 
 include</font></p>
 <ul>
 	<li>
@@ -4154,29 +4156,20 @@ include</font></p>
 	DAT ENVIRONMENT</font><font face="Courier New" size="2">:</font></h3>
 </div>
 <blockquote>
-	<p align="left"><font face="Courier New" size="2">DAT/DAPL v1.1 (free-build) 
-	runtime libraries are installed into %SystemRoot%, with the v1.1 Debug 
-	versions located in '%SystemDrive%\%ProgramFiles(x86)%\WinOF'.&nbsp; Debug 
-	libraries are identified as datd.dll and dapld.dll.</font></p>
-	<p align="left"><font face="Courier New" size="2">IA32 (aka, 32-bit) 
-	versions of DAT/DAPL 1.1 runtime libraries, found only on 64-bit systems, 
-	are identified in '%SystemDrive%\%ProgramFiles(x86)%\WinOF' as dat32.dll and 
-	dapl32.dll.<br>
-	<br>
-	DAT/DAPL 2.0 (free-build) libraries are identified in %SystemRoot% as 
+	<p align="left"><font face="Courier New" size="2">DAT/DAPL 2.0 (free-build) libraries are identified in %SystemRoot% as 
 	dat2.dll and dapl2.dll.&nbsp; Debug versions of the v2.0 runtime libraries 
-	are located in '%SystemDrive%\%ProgramFiles(x86)%\WinOF'.</font></p>
+	are located in '%SystemDrive%\%ProgramFiles%\WinOF'.</font></p>
 	<p align="left"><font face="Courier New" size="2">IA32 (aka, 32-bit) 
 	versions of DAT/DAPL 2.0 runtime libraries, found only on 64-bit systems, 
-	are identified in '%SystemDrive%\%ProgramFiles(x86)%\WinOF' as dat232.dll 
-	and dapl232.dll.</font></p>
-	<p align="left"><font face="Courier New" size="2">In order for DAT/uDAPL 
-	programs to execute correctly, the runtime library files 'dat.dll and 
-	dapl.dll' must be present in one of the following folders: current 
+	are identified in '%ProgramFiles%\WinOF' as dat32.dll 
+	and dapl32.dll.</font></p>
+	<p align="left"><font face="Courier New" size="2">In order for DAT/DAPL 
+	programs to execute correctly, the runtime library files 'dat2.dll and 
+	dapl2.dll' must be present in one of the following folders: current 
 	directory, %SystemRoot% or in the library search path.</font></p>
 	<p align="left"><font face="Courier New" size="2">The default WinOF 
-	installation places the runtime library files dat.dll and dapl.dll in the '%SystemRoot%' folder; 
-	symbol files (.pdb) are located in '%SystemDrive%\%ProgramFiles(x86)%\WinOF'.</font></p>
+	installation places the runtime library files dat2.dll and dapl2.dll in the '%SystemRoot%' folder; 
+	symbol files (.pdb) are located in '%ProgramFiles%\WinOF\'.</font></p>
 	<p align="left"><font face="Courier New" size="2">The default DAPL configuration 
 	file is defined as '%SystemDrive%\DAT\dat.conf'. This default 
 	specification can be overriden by use of the environment variable 
@@ -4184,7 +4177,7 @@ include</font></p>
 	<p align="left"><font face="Courier New" size="2">Within the dat.conf file, 
 	the DAPL library specification can be located as the 5th whitespace 
 	separated line argument. By default the DAPL library file is installed as
-	'%SystemRoot%\dapl.dll'.</font></p>
+	'%SystemRoot%\dapl2.dll'.</font></p>
 	<p align="left"><font face="Courier New" size="2">Should you choose to 
 	relocated the DAPL library file to a path where whitespace appears in the 
 	full library path specification, then the full library file specification 
@@ -4210,9 +4203,7 @@ include</font></p>
 	CM is IBAL).<br>&nbsp;&nbsp;&nbsp; ibnic1v2-scm - InfiniBand HCA #one, DAPL version 2.0, CM is 
 	'socket-CM'<br>
 &nbsp;&nbsp;&nbsp; ibnic0v2-cma - InfiniBand HCA #zero, DAPL version 2.0, CM is 
-	'rdma-CM'<br>
-&nbsp;&nbsp;&nbsp; ibnic0-scm&nbsp;&nbsp; - InfiniBand HCA #zero, DAPL version 1.1, CM is 
-	'IBAL'</font></p>
+	'rdma-CM'</font></p>
 	<p align="left"><font face="Courier New" size="2">Each non-comment line in 
 	the dat.conf file describes a DAPL provider interface.<br>
 	The 2nd to the last field on the right (7th from the left) describes the 
@@ -4295,10 +4286,9 @@ include</font></p>
 <p align="left"><b><u><a name="DAT_App_Build"></a>DAT application build environment</u>:</b></p>
 <blockquote>
 	<p align="left"><font face="Courier New" size="2">DAT library header files 
-	are selectively installed in the DAT default configuration folder as<br>'%SystemDrive%\DAT\v1-1' 
-	or
-	'%SystemDrive%\DAT\v2-0'. Your C language based DAT 1.1 application compilation command line 
-	should include'/I%SystemDrive%\DAT\v1-1' with C code referencing '#include &lt;DAT\udat.h&gt;'.<br>
+	are selectively installed in the DAT default configuration folder as<br>'%SystemDrive%\DAT\v2-0'. 
+	Your C language based DAT application compilation command line 
+	should include'/I%SystemDrive%\DAT\v2-0' with C code referencing '#include &lt;DAT\udat.h&gt;'.<br>
 	<br>
 	The 'default' DAT/DAPL C language calling convention is '__stdcall', not the 
 	'normal' Visual Studio C compiler default. __stdcall was chosen as MS 
@@ -4307,7 +4297,7 @@ include</font></p>
 	<br>
 	Visual Studio 2005 command window - (nmake) Makefile Fragments:</font></p>
 	<blockquote>
-		<p align="left"><font face="Courier New" size="2">DAT_PATH=%SystemDrive%\DAT\v1-1<br>
+		<p align="left"><font face="Courier New" size="2">DAT_PATH=%SystemDrive%\DAT\v2-0<br>
 		CC = cl<br>
 		INC_FLAGS = /I $(DAT_PATH)<br>
 		<br>
@@ -4321,8 +4311,7 @@ include</font></p>
 		<br>
 		LINK_FLAGS = /nologo /subsystem:console /machine:X64 
 		/libpath:$(DAT_PATH) $(LIBS)</font><b><br><br>
-		</b>When linking a DEBUG/Checked version make sure to use datd.lib or 
-		dat2d.lib for DAT v2.0.</p>
+		</b>When linking a DEBUG/Checked version make sure to use dat2d.lib .</p>
 	</blockquote>
 </blockquote>
 <h4><u>DAT library environment variables</u>:</h4>
@@ -4384,7 +4373,7 @@ debugging information, valid values are</font> <br><br></font>
 <h3><a name="DAPLTEST"></a>DAPLTEST</h3>
 <pre>
 
-    dapltest - test for the Direct Access Provider Library (DAPL)
+    dapltest - test for the Direct Access Provider Library (DAPL) v2.0
 
 DESCRIPTION
 
@@ -4392,8 +4381,8 @@ DESCRIPTION
     and verify the DAPL interfaces during development and porting.
     At least two instantiations of the test must be run.  One acts
     as the server, fielding requests and spawning server-side test
-    threads as needed.  Other client invocations connect to the
-    server and issue test requests.
+    threads as needed.  Other client invocation connects to the
+    Dapltest server and issue test requests.
 
     The server side of the test, once invoked, listens continuously
     for client connection requests, until quit or killed.  Upon
@@ -4629,35 +4618,35 @@ USAGE - Limit test client
 
 <a name="DAPLtest-examples"></a>EXAMPLES
 
-    dapltest -T S -d -D ibnic0
+    dapltest -T S -d -D ibnic0v2
 
                         Starts a local dapltest server process with debug verbosity.
                         Server loops (listen for dapltest request, process request).
     
-    dapltest -T T -d -s winIB -D ibnic0 -i 100 client SR 4096 2 server SR 4096 2
+    dapltest -T T -d -s winIB -D ibnic0v2 -i 100 client SR 4096 2 server SR 4096 2
 
                         Runs a transaction test, with both sides
                         sending one buffer with two 4KB segments,
                         one hundred times; dapltest server is on host winIB.
 
-    dapltest -T P -d -s winIB -D ibnic0 -i 100 RW 4096 2
+    dapltest -T P -d -s winIB -D ibnic0v2 -i 100 RW 4096 2
 
                         Runs a performance test, with the client 
                         RDMA writing one buffer with two 4KB segments,
                         one hundred times.
 
-    dapltest -T Q -s winIB -D ibnic0
+    dapltest -T Q -s winIB -D ibnic0v2
 
                         Asks the dapltest server at host 'winIB' to clean up and exit.
 
-    dapltest -T L -D ibnic0 -d -w 16 -m 1000
+    dapltest -T L -D ibnic0v2 -d -w 16 -m 1000
 
                         Runs all of the limit tests, setting up
                         16 complete sets of DAPL objects, and
                         creating at most a thousand instances
                         when trying to exhaust resources.
 
-    dapltest -T T -V -d -t 2 -w 4 -i 55555 -s winIB -D ibnic0 \
+    dapltest -T T -V -d -t 2 -w 4 -i 55555 -s winIB -D ibnic0v2 \
        client RW  4096 1    server RW  2048 4    \
        client SR  1024 4    server SR  4096 2    \
        client SR  1024 3 -f server SR  2048 1 -f
@@ -4668,7 +4657,7 @@ USAGE - Limit test client
                         for a larger number of iterations,
                         validating the data received.</pre>
 <pre>
-dt-svr.bat - DAPLtest server script; starts a DAPL2test.exe server on the local node.
+dt-svr.bat - DAPLtest server script; starts a DAPL2test.exe server on the local system.
 	dt-svr DAPL-provider [-D [hex-debug-bitmask] ]</pre>
 <blockquote>
 	<blockquote>
@@ -4695,9 +4684,9 @@ dt-svr.bat - DAPLtest server script; starts a DAPL2test.exe server on the local
 	dt-cli DAPL-provider host-IPv4-address testname [-D [hex-debug-bitmask] ]
 		example: dt-cli ibnic0v2 10.10.2.20 trans
 		         dt-cli -h  # outputs help text.
-			 dt-svr ibnic0v2	# IBAL on HCA0</pre>
+			 dt-svr ibnic0v2	# IBAL dapltest server listening on port HCA0</pre>
 <pre>
-Verify dt-*.bat script is running same dapltest.exe(v1.1) or dapl2test.exe(v2.0)
+Verify dt-*.bat script is running same dapl2test.exe(DAPL v2.0)
 
 
 BUGS  (and To Do List)
@@ -4730,15 +4719,21 @@ with a Subnet<br>
 Manager running somewhere on the IB fabric.<br>
 <br>
 - Supported Operating Systems and Service Packs:<br>
-&nbsp;&nbsp; o Windows XP SP3 x86 &amp; x64<br>
+&nbsp;&nbsp; o Windows 7 (x86 &amp; x64)<br>
+&nbsp;&nbsp; o Windows Server 2008 R2&nbsp; (x86, x64)<br>
 &nbsp;&nbsp; o Windows Server 2008/Vista&nbsp; (x86, x64)<br>
-&nbsp;&nbsp; o Windows Server 2008 HPC (x64)<br>
+&nbsp;&nbsp; o Windows Server 2008 HPC (x64,x86)<br>
 &nbsp;&nbsp; o Windows Server 2003 SP2/R2 (x86, x64, IA64)</p>
 <h4 align="left"><u>Testing Levels</u></h4>
 <p align="left">The SRP driver has undergone basic testing against Mellanox 
 Technologies'
 SRP Targets MTD1000 and MTD2000.<br>
-Additionally the Linux OFED 1.4 SRP target has been tested.<br>
+Additionally the Linux OFED 1.4.1 SRP target with scst 1.0.0.0 (vdisk with 
+blockio) has been tested.&nbsp; Note: ONLY the scst-1.0.0.0 release will work as 
+the OFED 1.4.1 ib_srpt driver has a symbol dependency on scst. later releases of 
+scst.ko no longer export the required symbol hence ib_srpt fails to load.<br>
+When ib_srpt is updated later versions of scst can be used.<br>
+<br>
 Testing included SRP target drive format, read, write and dismount/offline
 operations.<br>
 &nbsp;</p>
@@ -4782,6 +4777,168 @@ when the WinOF uninstall attempts to delete the files the operation fails.</p>
 <p align="left">SRP supports WPP tracing tools by using the GUID: 
 '5AF07B3C-D119-4233-9C81-C07EF481CBE6'.&nbsp; The flags and level of debug can be controlled at load-time or run-time; 
 see ib_srp.inf file for details.</p>
+<h4 align="left"><u>Constructing a RHEL 5.1 OFED 1.4.1 SRP vdisk BLOCKIO target</u></h4>
+<p align="left">Example assumptions:</p>
+<ul>
+	<li>
+	<p align="left">Red Hat Enterprise Linux Server release 5 (Tikanga) EL 5.1 
+	(2.6.18-8.el5)<br>
+	Later RHEL 5.4 releases will work with some minor scst compile time fixes 
+	and later OFED releases.</p></li>
+	<li>
+	<p align="left">Linux SRP Target has /dev/sdb[123]<br>
+	sizeof(sdb1) &lt; sdb2 &lt; sdb3; test convention only.</p></li>
+	<li>
+	<p align="left">scst-1.0.0.tgz is required as OFED 1.4.1 ib_srpt has symbol 
+	dependency on<br>
+	scst.ko....sigh. Later scst release do not export the required ib_srpt<br>
+	symbol; stick with scst-1.0.0 until OFED ib_srpt is updated.</p></li>
+	<li>
+	<p align="left"><a href="http://sourceforge.net/projects/scst/files/">
+	download scst-1.0.0</a></p></li>
+</ul>
+<p align="left">Use out of the box scst defines which include (#undef 
+STRICT_SERIALIZING),<br>
+'no' kernel mods are required for BLOCKIO access to /dev/sdb[123].<br>
+<br>
+cd scst-1.0.0.0<br>
+make all<br>
+make install<br>
+<br>
+cd OFED-1.4.1<br>
+build OFED select #3 for 'all' OFED components<br>
+&nbsp; - no SRP loads in /etc/infiniband/openib.conf, edit prior to reboot.</p>
+<p align="left">REBOOT.<br>
+<br>
+./LOAD &amp; ./UNLOAD scripts are manual versions of what scstAdmin (separate scst 
+package) will do minus<br>
+loading the OFED driver ib_srpt.<br>
+<br>
+SRP targets formatted from Windows using default NTFS allocation size.<br>
+Partition size &amp; numbering is derrived from local test conventions; your setup 
+will be different.<br>
+<br>
+/dev/sdb1 NTFS &lt; 1GB<br>
+/dev/sdb2 NTFS &gt; 1GB<br>
+/dev/sdb3 NTFS &gt; sdb2</p>
+<p align="left">&nbsp;</p>
+<h4 align="left"><u>Manual SRP Target LOAD script</u></h4>
+<div align="left">
+	<pre>#!/bin/sh 
+
+GRP=Default
+
+if [ ! -e /proc/scsi_tgt ] ; then
+  echo -n Loading scst driver
+  modprobe scst
+  if [ $? -ne 0 ] ; then
+    echo
+    echo err $? modprobe scst
+    exit $?
+  fi
+  echo ...OK
+fi 
+
+if [ ! -e /proc/scsi_tgt/vdisk ] ; then
+  echo -n Loading scst_vdisk driver
+  modprobe scst_vdisk
+  if [ $? -ne 0 ] ; then
+    echo
+    echo err $? modprobe scst_vdisk
+    exit $?
+  fi
+  echo ...OK
+fi 
+
+if [ ! -e /proc/scsi_tgt/vdisk ] ; then
+  echo -n Loading scst_vdisk driver
+  modprobe scst_vdisk
+  if [ $? -ne 0 ] ; then
+    echo
+    echo err $? modprobe scst_vdisk
+    exit $?
+  fi
+  echo ...OK
+fi 
+
+fgrep -q ib_srpt /proc/modules
+if [ $? -ne 0 ] ; then
+  modprobe ib_srpt
+  echo ib_srpt...OK
+fi 
+
+echo -n Open SRP devices srp[123]
+echo &quot;open srp1 /dev/sdb1 512 BLOCKIO&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+if [ $? -ne 0 ] ; then
+  echo err $? open srp1 /dev/sdb1
+  exit $?
+fi
+echo &quot;open srp2 /dev/sdb2 512 BLOCKIO&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+if [ $? -ne 0 ] ; then
+  echo err $? open srp2 /dev/sdb2
+  exit $?
+fi
+echo &quot;open srp3 /dev/sdb3 512 BLOCKIO&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+if [ $? -ne 0 ] ; then
+  echo err $? open srp3 /dev/sdb3
+  exit $?
+fi
+echo ...OK
+
+echo -n Set allowed hosts access...
+echo &quot;add *&quot; &gt; /proc/scsi_tgt/groups/Default/names
+echo ...OK
+
+echo -n Adding targets srp[123] as LUNs [012] in group $GRP
+echo &quot;add srp1 0&quot; &gt; /proc/scsi_tgt/groups/Default/devices
+if [ $? -ne 0 ] ; then
+  echo
+  echo err $? add srp1 0
+  exit $?
+fi
+echo &quot;add srp2 1&quot; &gt; /proc/scsi_tgt/groups/Default/devices
+if [ $? -ne 0 ] ; then
+  echo
+  echo err $? add srp2 1
+  exit $?
+fi
+echo &quot;add srp3 2&quot; &gt; /proc/scsi_tgt/groups/Default/devices
+if [ $? -ne 0 ] ; then
+  echo
+  echo err $? add srp3 2
+  exit $?
+fi
+echo ...OK
+</pre>
+</div>
+<div align="left">
+	<h4 align="left"><u>Manual SRP Target UNLOAD script</u></h4>
+	<pre>#!/bin/sh
+
+if [ -w /proc/scsi_tgt/vdisk/vdisk ] ; then
+  echo -n Closing SRP Targets srp[321]...
+  echo &quot;close srp3&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+  echo &quot;close srp2&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+  echo &quot;close srp1&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+  echo Done.
+fi
+
+fgrep -q scst_vdisk /proc/modules
+if [ $? -eq 0 ] ; then
+  modprobe -r scst_vdisk
+fi
+
+fgrep -q ib_srpt /proc/modules
+if [ $? -eq 0 ] ; then
+  modprobe -r ib_srpt
+fi
+
+fgrep -q scst /proc/modules
+if [ $? -eq 0 ] ; then
+  modprobe -r scst
+fi
+</pre>
+</div>
 <h4 align="left"><a href="#TOP"><font color="#000000" size="4">&lt;return-to-top&gt;</font></a></h4>
 <h3>&nbsp;</h3>
 <BLOCKQUOTE></BLOCKQUOTE>
diff --git a/trunk/docs/Manual.htm b/trunk/docs/Manual.htm
index d9562227..0498658c 100644
--- a/trunk/docs/Manual.htm
+++ b/trunk/docs/Manual.htm
@@ -13,9 +13,9 @@ div.Section1
 <a href="#TOP"></a> </h1>
 <h1 align="center">Windows OpenFabrics </h1>
 <h1 align="center">User's Manual</h1>
-<h2 align="center">Release 2.1</h2>
+<h2 align="center">Release 2.2</h2>
 <h3 align="center">
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->12/10/2009<!--webbot bot="Timestamp" endspan i-checksum="12507" --></h3>
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->12/29/2009<!--webbot bot="Timestamp" endspan i-checksum="12659" --></h3>
 <h2 align="left"><u>Overview</u></h2>
 <p align="left"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'">
 The Windows OpenFabrics (WinOF) package is composed of software modules intended 
@@ -90,7 +90,7 @@ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none;
 	<br>&nbsp;</li>
 </ul></li>
 	<li>
-	<h3 align="left"><a href="#SRP">SRP (SCSI RDMA) Protocol Driver</a></h3></li>
+	<h3 align="left"><a href="#SRP">SRP (SCSI over RDMA) Protocol Driver</a></h3></li>
 	<li>
 	<h3 align="left"><u><font color="#0000FF"><a href="#QLOGICVNIC">QLogic VNIC_Driver</a></font></u></h3></li>
 	<li>
@@ -4066,13 +4066,15 @@ order provide a set of transport-independent, platform-independent Application
 Programming Interfaces that exploit the RDMA (remote direct memory access) 
 capabilities of next-generation interconnect technologies such as InfiniBand, 
 and iWARP.</font></p>
-<p align="left"><font face="Times New Roman">WinOF DAT and DAPL are based on the 1.1 DAT specification. The DAPL 
+<p align="left"><font face="Times New Roman">WinOF uDAT and uDAPL are based on the 
+2.0 DAT specification. The DAPL 
 (Direct Access Provider Library) which now fully supports Infiniband RDMA and 
 IPoIB.</font></p>
-<p align="left"><font face="Times New Roman">WinOF 1.0.1, and future WinOF 
-releases, will include DAT/DAPL version 2.0 runtime libraries along with an optional 
-v2.0 application build environment.<br>
-DAT 2.0 is configured with InfiniBand extensions enabled. The IB extensions 
+<p align="left"><font face="Times New Roman">Previous WinOF 
+releases supported the uDAT/uDAPL 1.1 provider which has now been deprecated.<br>
+uDAT/uDAPL version 2.0 runtime libraries along with an optional 
+v2.0 application build environment are the only options.<br>
+uDAT 2.0 is configured with InfiniBand extensions enabled. The IB extensions 
 include</font></p>
 <ul>
 	<li>
@@ -4154,29 +4156,20 @@ include</font></p>
 	DAT ENVIRONMENT</font><font face="Courier New" size="2">:</font></h3>
 </div>
 <blockquote>
-	<p align="left"><font face="Courier New" size="2">DAT/DAPL v1.1 (free-build) 
-	runtime libraries are installed into %SystemRoot%, with the v1.1 Debug 
-	versions located in '%SystemDrive%\%ProgramFiles(x86)%\WinOF'.&nbsp; Debug 
-	libraries are identified as datd.dll and dapld.dll.</font></p>
-	<p align="left"><font face="Courier New" size="2">IA32 (aka, 32-bit) 
-	versions of DAT/DAPL 1.1 runtime libraries, found only on 64-bit systems, 
-	are identified in '%SystemDrive%\%ProgramFiles(x86)%\WinOF' as dat32.dll and 
-	dapl32.dll.<br>
-	<br>
-	DAT/DAPL 2.0 (free-build) libraries are identified in %SystemRoot% as 
+	<p align="left"><font face="Courier New" size="2">DAT/DAPL 2.0 (free-build) libraries are identified in %SystemRoot% as 
 	dat2.dll and dapl2.dll.&nbsp; Debug versions of the v2.0 runtime libraries 
-	are located in '%SystemDrive%\%ProgramFiles(x86)%\WinOF'.</font></p>
+	are located in '%SystemDrive%\%ProgramFiles%\WinOF'.</font></p>
 	<p align="left"><font face="Courier New" size="2">IA32 (aka, 32-bit) 
 	versions of DAT/DAPL 2.0 runtime libraries, found only on 64-bit systems, 
-	are identified in '%SystemDrive%\%ProgramFiles(x86)%\WinOF' as dat232.dll 
-	and dapl232.dll.</font></p>
-	<p align="left"><font face="Courier New" size="2">In order for DAT/uDAPL 
-	programs to execute correctly, the runtime library files 'dat.dll and 
-	dapl.dll' must be present in one of the following folders: current 
+	are identified in '%ProgramFiles%\WinOF' as dat32.dll 
+	and dapl32.dll.</font></p>
+	<p align="left"><font face="Courier New" size="2">In order for DAT/DAPL 
+	programs to execute correctly, the runtime library files 'dat2.dll and 
+	dapl2.dll' must be present in one of the following folders: current 
 	directory, %SystemRoot% or in the library search path.</font></p>
 	<p align="left"><font face="Courier New" size="2">The default WinOF 
-	installation places the runtime library files dat.dll and dapl.dll in the '%SystemRoot%' folder; 
-	symbol files (.pdb) are located in '%SystemDrive%\%ProgramFiles(x86)%\WinOF'.</font></p>
+	installation places the runtime library files dat2.dll and dapl2.dll in the '%SystemRoot%' folder; 
+	symbol files (.pdb) are located in '%ProgramFiles%\WinOF\'.</font></p>
 	<p align="left"><font face="Courier New" size="2">The default DAPL configuration 
 	file is defined as '%SystemDrive%\DAT\dat.conf'. This default 
 	specification can be overriden by use of the environment variable 
@@ -4184,7 +4177,7 @@ include</font></p>
 	<p align="left"><font face="Courier New" size="2">Within the dat.conf file, 
 	the DAPL library specification can be located as the 5th whitespace 
 	separated line argument. By default the DAPL library file is installed as
-	'%SystemRoot%\dapl.dll'.</font></p>
+	'%SystemRoot%\dapl2.dll'.</font></p>
 	<p align="left"><font face="Courier New" size="2">Should you choose to 
 	relocated the DAPL library file to a path where whitespace appears in the 
 	full library path specification, then the full library file specification 
@@ -4210,9 +4203,7 @@ include</font></p>
 	CM is IBAL).<br>&nbsp;&nbsp;&nbsp; ibnic1v2-scm - InfiniBand HCA #one, DAPL version 2.0, CM is 
 	'socket-CM'<br>
 &nbsp;&nbsp;&nbsp; ibnic0v2-cma - InfiniBand HCA #zero, DAPL version 2.0, CM is 
-	'rdma-CM'<br>
-&nbsp;&nbsp;&nbsp; ibnic0-scm&nbsp;&nbsp; - InfiniBand HCA #zero, DAPL version 1.1, CM is 
-	'IBAL'</font></p>
+	'rdma-CM'</font></p>
 	<p align="left"><font face="Courier New" size="2">Each non-comment line in 
 	the dat.conf file describes a DAPL provider interface.<br>
 	The 2nd to the last field on the right (7th from the left) describes the 
@@ -4295,10 +4286,9 @@ include</font></p>
 <p align="left"><b><u><a name="DAT_App_Build"></a>DAT application build environment</u>:</b></p>
 <blockquote>
 	<p align="left"><font face="Courier New" size="2">DAT library header files 
-	are selectively installed in the DAT default configuration folder as<br>'%SystemDrive%\DAT\v1-1' 
-	or
-	'%SystemDrive%\DAT\v2-0'. Your C language based DAT 1.1 application compilation command line 
-	should include'/I%SystemDrive%\DAT\v1-1' with C code referencing '#include &lt;DAT\udat.h&gt;'.<br>
+	are selectively installed in the DAT default configuration folder as<br>'%SystemDrive%\DAT\v2-0'. 
+	Your C language based DAT application compilation command line 
+	should include'/I%SystemDrive%\DAT\v2-0' with C code referencing '#include &lt;DAT\udat.h&gt;'.<br>
 	<br>
 	The 'default' DAT/DAPL C language calling convention is '__stdcall', not the 
 	'normal' Visual Studio C compiler default. __stdcall was chosen as MS 
@@ -4307,7 +4297,7 @@ include</font></p>
 	<br>
 	Visual Studio 2005 command window - (nmake) Makefile Fragments:</font></p>
 	<blockquote>
-		<p align="left"><font face="Courier New" size="2">DAT_PATH=%SystemDrive%\DAT\v1-1<br>
+		<p align="left"><font face="Courier New" size="2">DAT_PATH=%SystemDrive%\DAT\v2-0<br>
 		CC = cl<br>
 		INC_FLAGS = /I $(DAT_PATH)<br>
 		<br>
@@ -4321,8 +4311,7 @@ include</font></p>
 		<br>
 		LINK_FLAGS = /nologo /subsystem:console /machine:X64 
 		/libpath:$(DAT_PATH) $(LIBS)</font><b><br><br>
-		</b>When linking a DEBUG/Checked version make sure to use datd.lib or 
-		dat2d.lib for DAT v2.0.</p>
+		</b>When linking a DEBUG/Checked version make sure to use dat2d.lib .</p>
 	</blockquote>
 </blockquote>
 <h4><u>DAT library environment variables</u>:</h4>
@@ -4384,7 +4373,7 @@ debugging information, valid values are</font> <br><br></font>
 <h3><a name="DAPLTEST"></a>DAPLTEST</h3>
 <pre>
 
-    dapltest - test for the Direct Access Provider Library (DAPL)
+    dapltest - test for the Direct Access Provider Library (DAPL) v2.0
 
 DESCRIPTION
 
@@ -4392,8 +4381,8 @@ DESCRIPTION
     and verify the DAPL interfaces during development and porting.
     At least two instantiations of the test must be run.  One acts
     as the server, fielding requests and spawning server-side test
-    threads as needed.  Other client invocations connect to the
-    server and issue test requests.
+    threads as needed.  Other client invocation connects to the
+    Dapltest server and issue test requests.
 
     The server side of the test, once invoked, listens continuously
     for client connection requests, until quit or killed.  Upon
@@ -4629,35 +4618,35 @@ USAGE - Limit test client
 
 <a name="DAPLtest-examples"></a>EXAMPLES
 
-    dapltest -T S -d -D ibnic0
+    dapltest -T S -d -D ibnic0v2
 
                         Starts a local dapltest server process with debug verbosity.
                         Server loops (listen for dapltest request, process request).
     
-    dapltest -T T -d -s winIB -D ibnic0 -i 100 client SR 4096 2 server SR 4096 2
+    dapltest -T T -d -s winIB -D ibnic0v2 -i 100 client SR 4096 2 server SR 4096 2
 
                         Runs a transaction test, with both sides
                         sending one buffer with two 4KB segments,
                         one hundred times; dapltest server is on host winIB.
 
-    dapltest -T P -d -s winIB -D ibnic0 -i 100 RW 4096 2
+    dapltest -T P -d -s winIB -D ibnic0v2 -i 100 RW 4096 2
 
                         Runs a performance test, with the client 
                         RDMA writing one buffer with two 4KB segments,
                         one hundred times.
 
-    dapltest -T Q -s winIB -D ibnic0
+    dapltest -T Q -s winIB -D ibnic0v2
 
                         Asks the dapltest server at host 'winIB' to clean up and exit.
 
-    dapltest -T L -D ibnic0 -d -w 16 -m 1000
+    dapltest -T L -D ibnic0v2 -d -w 16 -m 1000
 
                         Runs all of the limit tests, setting up
                         16 complete sets of DAPL objects, and
                         creating at most a thousand instances
                         when trying to exhaust resources.
 
-    dapltest -T T -V -d -t 2 -w 4 -i 55555 -s winIB -D ibnic0 \
+    dapltest -T T -V -d -t 2 -w 4 -i 55555 -s winIB -D ibnic0v2 \
        client RW  4096 1    server RW  2048 4    \
        client SR  1024 4    server SR  4096 2    \
        client SR  1024 3 -f server SR  2048 1 -f
@@ -4668,7 +4657,7 @@ USAGE - Limit test client
                         for a larger number of iterations,
                         validating the data received.</pre>
 <pre>
-dt-svr.bat - DAPLtest server script; starts a DAPL2test.exe server on the local node.
+dt-svr.bat - DAPLtest server script; starts a DAPL2test.exe server on the local system.
 	dt-svr DAPL-provider [-D [hex-debug-bitmask] ]</pre>
 <blockquote>
 	<blockquote>
@@ -4695,9 +4684,9 @@ dt-svr.bat - DAPLtest server script; starts a DAPL2test.exe server on the local
 	dt-cli DAPL-provider host-IPv4-address testname [-D [hex-debug-bitmask] ]
 		example: dt-cli ibnic0v2 10.10.2.20 trans
 		         dt-cli -h  # outputs help text.
-			 dt-svr ibnic0v2	# IBAL on HCA0</pre>
+			 dt-svr ibnic0v2	# IBAL dapltest server listening on port HCA0</pre>
 <pre>
-Verify dt-*.bat script is running same dapltest.exe(v1.1) or dapl2test.exe(v2.0)
+Verify dt-*.bat script is running same dapl2test.exe(DAPL v2.0)
 
 
 BUGS  (and To Do List)
@@ -4730,15 +4719,21 @@ with a Subnet<br>
 Manager running somewhere on the IB fabric.<br>
 <br>
 - Supported Operating Systems and Service Packs:<br>
-&nbsp;&nbsp; o Windows XP SP3 x86 &amp; x64<br>
+&nbsp;&nbsp; o Windows 7 (x86 &amp; x64)<br>
+&nbsp;&nbsp; o Windows Server 2008 R2&nbsp; (x86, x64)<br>
 &nbsp;&nbsp; o Windows Server 2008/Vista&nbsp; (x86, x64)<br>
-&nbsp;&nbsp; o Windows Server 2008 HPC (x64)<br>
+&nbsp;&nbsp; o Windows Server 2008 HPC (x64,x86)<br>
 &nbsp;&nbsp; o Windows Server 2003 SP2/R2 (x86, x64, IA64)</p>
 <h4 align="left"><u>Testing Levels</u></h4>
 <p align="left">The SRP driver has undergone basic testing against Mellanox 
 Technologies'
 SRP Targets MTD1000 and MTD2000.<br>
-Additionally the Linux OFED 1.4 SRP target has been tested.<br>
+Additionally the Linux OFED 1.4.1 SRP target with scst 1.0.0.0 (vdisk with 
+blockio) has been tested.&nbsp; Note: ONLY the scst-1.0.0.0 release will work as 
+the OFED 1.4.1 ib_srpt driver has a symbol dependency on scst. later releases of 
+scst.ko no longer export the required symbol hence ib_srpt fails to load.<br>
+When ib_srpt is updated later versions of scst can be used.<br>
+<br>
 Testing included SRP target drive format, read, write and dismount/offline
 operations.<br>
 &nbsp;</p>
@@ -4782,6 +4777,168 @@ when the WinOF uninstall attempts to delete the files the operation fails.</p>
 <p align="left">SRP supports WPP tracing tools by using the GUID: 
 '5AF07B3C-D119-4233-9C81-C07EF481CBE6'.&nbsp; The flags and level of debug can be controlled at load-time or run-time; 
 see ib_srp.inf file for details.</p>
+<h4 align="left"><u>Constructing a RHEL 5.1 OFED 1.4.1 SRP vdisk BLOCKIO target</u></h4>
+<p align="left">Example assumptions:</p>
+<ul>
+	<li>
+	<p align="left">Red Hat Enterprise Linux Server release 5 (Tikanga) EL 5.1 
+	(2.6.18-8.el5)<br>
+	Later RHEL 5.4 releases will work with some minor scst compile time fixes 
+	and later OFED releases.</p></li>
+	<li>
+	<p align="left">Linux SRP Target has /dev/sdb[123]<br>
+	sizeof(sdb1) &lt; sdb2 &lt; sdb3; test convention only.</p></li>
+	<li>
+	<p align="left">scst-1.0.0.tgz is required as OFED 1.4.1 ib_srpt has symbol 
+	dependency on<br>
+	scst.ko....sigh. Later scst release do not export the required ib_srpt<br>
+	symbol; stick with scst-1.0.0 until OFED ib_srpt is updated.</p></li>
+	<li>
+	<p align="left"><a href="http://sourceforge.net/projects/scst/files/">
+	download scst-1.0.0</a></p></li>
+</ul>
+<p align="left">Use out of the box scst defines which include (#undef 
+STRICT_SERIALIZING),<br>
+'no' kernel mods are required for BLOCKIO access to /dev/sdb[123].<br>
+<br>
+cd scst-1.0.0.0<br>
+make all<br>
+make install<br>
+<br>
+cd OFED-1.4.1<br>
+build OFED select #3 for 'all' OFED components<br>
+&nbsp; - no SRP loads in /etc/infiniband/openib.conf, edit prior to reboot.</p>
+<p align="left">REBOOT.<br>
+<br>
+./LOAD &amp; ./UNLOAD scripts are manual versions of what scstAdmin (separate scst 
+package) will do minus<br>
+loading the OFED driver ib_srpt.<br>
+<br>
+SRP targets formatted from Windows using default NTFS allocation size.<br>
+Partition size &amp; numbering is derrived from local test conventions; your setup 
+will be different.<br>
+<br>
+/dev/sdb1 NTFS &lt; 1GB<br>
+/dev/sdb2 NTFS &gt; 1GB<br>
+/dev/sdb3 NTFS &gt; sdb2</p>
+<p align="left">&nbsp;</p>
+<h4 align="left"><u>Manual SRP Target LOAD script</u></h4>
+<div align="left">
+	<pre>#!/bin/sh 
+
+GRP=Default
+
+if [ ! -e /proc/scsi_tgt ] ; then
+  echo -n Loading scst driver
+  modprobe scst
+  if [ $? -ne 0 ] ; then
+    echo
+    echo err $? modprobe scst
+    exit $?
+  fi
+  echo ...OK
+fi 
+
+if [ ! -e /proc/scsi_tgt/vdisk ] ; then
+  echo -n Loading scst_vdisk driver
+  modprobe scst_vdisk
+  if [ $? -ne 0 ] ; then
+    echo
+    echo err $? modprobe scst_vdisk
+    exit $?
+  fi
+  echo ...OK
+fi 
+
+if [ ! -e /proc/scsi_tgt/vdisk ] ; then
+  echo -n Loading scst_vdisk driver
+  modprobe scst_vdisk
+  if [ $? -ne 0 ] ; then
+    echo
+    echo err $? modprobe scst_vdisk
+    exit $?
+  fi
+  echo ...OK
+fi 
+
+fgrep -q ib_srpt /proc/modules
+if [ $? -ne 0 ] ; then
+  modprobe ib_srpt
+  echo ib_srpt...OK
+fi 
+
+echo -n Open SRP devices srp[123]
+echo &quot;open srp1 /dev/sdb1 512 BLOCKIO&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+if [ $? -ne 0 ] ; then
+  echo err $? open srp1 /dev/sdb1
+  exit $?
+fi
+echo &quot;open srp2 /dev/sdb2 512 BLOCKIO&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+if [ $? -ne 0 ] ; then
+  echo err $? open srp2 /dev/sdb2
+  exit $?
+fi
+echo &quot;open srp3 /dev/sdb3 512 BLOCKIO&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+if [ $? -ne 0 ] ; then
+  echo err $? open srp3 /dev/sdb3
+  exit $?
+fi
+echo ...OK
+
+echo -n Set allowed hosts access...
+echo &quot;add *&quot; &gt; /proc/scsi_tgt/groups/Default/names
+echo ...OK
+
+echo -n Adding targets srp[123] as LUNs [012] in group $GRP
+echo &quot;add srp1 0&quot; &gt; /proc/scsi_tgt/groups/Default/devices
+if [ $? -ne 0 ] ; then
+  echo
+  echo err $? add srp1 0
+  exit $?
+fi
+echo &quot;add srp2 1&quot; &gt; /proc/scsi_tgt/groups/Default/devices
+if [ $? -ne 0 ] ; then
+  echo
+  echo err $? add srp2 1
+  exit $?
+fi
+echo &quot;add srp3 2&quot; &gt; /proc/scsi_tgt/groups/Default/devices
+if [ $? -ne 0 ] ; then
+  echo
+  echo err $? add srp3 2
+  exit $?
+fi
+echo ...OK
+</pre>
+</div>
+<div align="left">
+	<h4 align="left"><u>Manual SRP Target UNLOAD script</u></h4>
+	<pre>#!/bin/sh
+
+if [ -w /proc/scsi_tgt/vdisk/vdisk ] ; then
+  echo -n Closing SRP Targets srp[321]...
+  echo &quot;close srp3&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+  echo &quot;close srp2&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+  echo &quot;close srp1&quot; &gt; /proc/scsi_tgt/vdisk/vdisk
+  echo Done.
+fi
+
+fgrep -q scst_vdisk /proc/modules
+if [ $? -eq 0 ] ; then
+  modprobe -r scst_vdisk
+fi
+
+fgrep -q ib_srpt /proc/modules
+if [ $? -eq 0 ] ; then
+  modprobe -r ib_srpt
+fi
+
+fgrep -q scst /proc/modules
+if [ $? -eq 0 ] ; then
+  modprobe -r scst
+fi
+</pre>
+</div>
 <h4 align="left"><a href="#TOP"><font color="#000000" size="4">&lt;return-to-top&gt;</font></a></h4>
 <h3>&nbsp;</h3>
 <BLOCKQUOTE></BLOCKQUOTE>