\r
-[8-5-09] WinOF 2.1 RC-3 release\r
+[8-20-09] WinOF 2.1 RC-4 release\r
+\r
+Downloads available at http://www.openfabrics.org/downloads/WinOF/v2.1-RC4\r
+\r
+RC4 Changes:\r
+\r
+SVN Commits\r
+\r
+2372 - [DAPL2] Completion Channel refactoring\r
+ Modified : /gen1/branches/WOF2-1/etc/user/comp_channel.cpp\r
+ Modified : /gen1/branches/WOF2-1/inc/user/comp_channel.h\r
+ Modified : /gen1/branches/WOF2-1/ulp/dapl2/dapl/openib_cma/device.c\r
+ Modified : /gen1/branches/WOF2-1/ulp/dapl2/dapl/openib_scm/device.c\r
+\r
+2371 - [DAPL2] dapltest.exe: yield the processor as the Windows thread scheduler will starve other\r
+ threads unlike the Linux scheduler.\r
+ Modified : /gen1/branches/WOF2-1/ulp/dapl2/test/dapltest/mdep/linux/dapl_mdep_user.h\r
+ Modified : /gen1/branches/WOF2-1/ulp/dapl2/test/dapltest/mdep/solaris/dapl_mdep_user.h\r
+ Modified : /gen1/branches/WOF2-1/ulp/dapl2/test/dapltest/mdep/windows/dapl_mdep_user.h\r
+ Modified : /gen1/branches/WOF2-1/ulp/dapl2/test/dapltest/test/dapl_test_util.c\r
+\r
+2370,2369 [WIX]\r
+ wix\win7\x64\wof.wxs: added comment indicating Win7_x64 installer was for Server 2008 R2 also.\r
+ WIX/build-OFA-dist.bat: update usage instructions to reflect WinOF is now under Trunk\ and\r
+ no longer under branches. \r
+\r
+2368 - [DAPL2] dt-cli.bat: %ERRORLEVEL% inside a for loop does not evaluate as expected; change to !ERRORLEVEL!\r
+2367 - [DOCS] manual.htm: Update DAPL provider text w.r.t. names in DAT.conf file.\r
+2364 - [IPOIB] IPoIB PXE boot support: Clear remainder of chaddr\r
+ The IPoIB PXE boot firmware (gPXE) now sends the 8-byte port GUID in\r
+ the DHCP chaddr field. WinOF replaces the first 6 bytes of chaddr\r
+ with the Ethernet-style MAC address, but leaves the remain untouched.\r
+ This results in trailing garbage after the Ethernet-style MAC in the modified chaddr.\r
+ Fix by explicitly zeroing the remainder of chaddr.\r
+ Modified : /gen1/branches/WOF2-1/ulp/ipoib/kernel/ipoib_port.c\r
+\r
+2363 - [IBAT] allow simultaneous IBAT device access from user mode by adding RW sharing\r
+ attributes to CreateFileW() call.\r
+ Modified : /gen1/branches/WOF2-1/core/ibat/user/ibat.cpp\r
+2362 - [LIBRDMACM] retry IBAT call on E_PENDING return.\r
+ Modified : /gen1/branches/WOF2-1/ulp/librdmacm/src/cma.cpp\r
+\r
+2361 - [MLX4] on catastrophic error, dump error buffer before reset. [winof: 2358]\r
+ Modified : /gen1/branches/WOF2-1/hw/mlx4/kernel/bus/net/catas.c\r
+\r
+2360 - [MLX4] bug fix in error flow: doesn't return error on allocation failure. [winof: 2356]\r
+ Modified : /gen1/branches/WOF2-1/hw/mlx4/kernel/bus/core/l2w_umem.c\r
+\r
+2359 - [IBAL] fix to 2226. cause an asynchronic event to be handled immediately (and not after SMI_POLL_INTERVAL,\r
+ which is 20 secs)\r
+ Modified : /gen1/branches/WOF2-1/core/al/al_ci_ca_shared.c\r
+ Modified : /gen1/branches/WOF2-1/core/al/kernel/al_pnp.c\r
+\r
+2353 - [ND provider] patch to fix to 2333. Eemove a facility to define MaxDataInlineSize from application,\r
+ because it breaks MS API\r
+ [ND porvider] Improved latency of ND provider by using INLINE send. [winof: 2333, 2352]\r
+ This patch adds usage of INLINE DATA facility of Mellanox HCAs for improving latency of ND provider.\r
+ Ideas of the patch:\r
+ - by default, ND provider will create QP with inline data of 160 bytes;\r
+ (this can enlarge user's QP size)\r
+ - one can change this default by defining environment variable IBNDPROV_MAX_INLINE_SIZE;\r
+\r
+ Modified : /gen1/branches/WOF2-1/ulp/nd/user/NdEndpoint.cpp\r
+ Modified : /gen1/branches/WOF2-1/ulp/nd/user/NdEndpoint.h\r
+ Modified : /gen1/branches/WOF2-1/ulp/nd/user/NdProv.cpp\r
+\r
+2351 - [IPOIB] Prevent a BSOD which happens when restarting the opensm more than once\r
+ (if the local endpoint was not in the lid_endpts list).\r
+ Modified : /gen1/branches/WOF2-1/ulp/ipoib/kernel/ipoib_port.c\r
+ Modified : /gen1/trunk/ulp/ipoib/kernel/ipoib_port.c\r
\r
-Downloads available at http://www.openfabrics.org/downloads/WinOF/v2.1-RC3\r
-\r
-RC3 Changes:\r
-\r
-DAPL V2 CNO & CQ fixes.\r
-DAT include corrected to for IPv4 IPv6 sockaddr - include winsock2.h & w2tcpip.h\r
-Event completion channel fixes for DAPL; etc\user\comp_chan.cpp\r
-\r
-For Svr2008 installs, see HPC example scripts @ '%ProgramFiles(x86)%\WinOF\HPC' \r
\r
WinOF 2.1 Summary Changes \r
-------------------------\r
\r
1) The WinOF 2.1 release is based on openib-windows source svn revision\r
- (branches\WOF2-1 svn.2327).\r
+ (branches\WOF2-1 svn.2375).\r
\r
Last WinOF release (2.0.2) based on svn.1975.\r
\r
\r
- ndinstall.exe command line interface changes - see manual.htm\r
\r
-5) Vista installs Only:\r
+5) Technology Previews\r
+\r
+ DAPL2 Socket-CM provider\r
+ Uses IPv4 sockets to exchange Queue pair setup information, thus bypassing IB\r
+ Path Record lookups.\r
+\r
+ DAPL rdma-CM\r
+ Compatible with OFED rdma-CM interfaces; facilates IB application portability\r
+ between Linux/OFED and Windows/WinOF.\r
+ \r
+\r
+6) Vista installs Only:\r
\r
Vista installs must be performed from an Administrator priviledged command\r
window. Right-clicking the .msi installer file for a Vista installation\r
<h1 align=center style='text-align:center'><a name="WinOF_Release_Notes">2.1 Release Notes</a></h1>\r
\r
<h3 align=center style='text-align:center'>\r
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->08/04/2009<!--webbot bot="Timestamp" endspan i-checksum="12574" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->08/19/2009<!--webbot bot="Timestamp" endspan i-checksum="12662" --></h3>\r
\r
<div class=MsoNormal align=center style='text-align:center'>\r
\r
<p class=MsoPlainText><span style='font-size:12.0pt;font-family:"Arial"'> Binary\r
files generated from the OpenIB-windows developers subversion (svn) source tree </span>\r
<font face="Arial">'svn://openib.tc.cornell.edu'<span style='font-size:12.0pt;'> \r
-(branches\WOF2-1 svn revision <font color="#FF0000">2327</font>)\r
+(branches\WOF2-1 svn revision <font color="#FF0000">2375</font>)\r
are packaged into a <a href="http://www.dalun.com/wix/default.htm">WIX 2.0 \r
(Windows Installer Xml)</a> single file install package referred to as the \r
Windows OpenFabrics (WinOF) release 2.1.</span></font><span style='font-size:12.0pt;font-family:"Times New Roman"'><br>\r
the install console for instructions as what to do (Install, Trust or not)?<br>\r
This prompting results in a failed remote node install when performing a \r
<font color="#FF0000">first-time</font> unattended WinOF install.<br>\r
-By preloading the remote node's Trusted 3rd party Software Publisher certificate \r
+By preloading the remote node's Trusted 3rd party Software Publisher Certificate \r
Store, the unattended install will proceed without prompting, thus allowing the WinOF install to complete \r
successfully.</font></p>\r
<p><font face="Arial">Be aware: if a node is reimaged (same or different template applied) the \r
who choose to use it. Static IP address binding allows a direct mapping from \r
IP address to physical node number.<br>\r
</font></li>\r
- <li><font face="Arial">At this juncture, the WinOF drivers are installed.<br> </font></li>\r
+ <li><font face="Arial">IPoIB static IPv4 address assignment points of \r
+ Interest<br>\r
+ When installing WinOF one must consider how the Interface name 'Local Area \r
+ Connection {x}' is assigned to the IPoIB ports in order to correctly target \r
+ IP address assignment. <br>\r
+ Assume the target compute node has two Ethernet port and your HCA has two IB \r
+ ports. After the 1st WinOF installation, or node reprovisioing \r
+ you will see the following assignments:</font><ul>\r
+ <li><font face="Arial">Ethernet port 0 is 'Local Area Connection'</font></li>\r
+ <li><font face="Arial">Ethernet port 1 is 'Local Area Connection 2'</font></li>\r
+ <li><font face="Arial">IB port 1 is 'Local Area Connection 3'</font></li>\r
+ <li><font face="Arial">IB port 2 is 'Local Area Connection 4'</font></li>\r
+</ul>\r
+ <p><font face="Arial">A few minutes after the WinOF install completes, the \r
+ HPC manager will rename the active IPoIB 'Local Area Connection 3' network \r
+ interface to the 'Application' network interface along with the active \r
+ Ethernet interface being renamed to the 'Private' network; 'Local Area \r
+ Connection' is no longer in use.<br>\r
+ If WinOF is uninstalled and then reinstalled without node reprovisioning, \r
+ the active IPoIB network interface is installed as 'Local Area Connection'. \r
+ Within a few minutes, the active IPoIB network interface will again be \r
+ renamed the 'Application' network interface.<br>\r
+ Summary:<br>\r
+ 1st WinOF install, an IB cable is attached to HCA port 1, \r
+ IPoIB is named 'Local Area Connection 3'.<br>\r
+ 2nd WinOF install, IPoIB is named 'Local Area Connection' as \r
+ the Ethernet interface is renamed the 'Private' network.<br>\r
+ </font></li>\r
+ <li><font face="Arial">At this juncture, the WinOF drivers are installed.<br>\r
+ </font></li>\r
</ul>\r
<h3><u>Windows Deployment Manager usage for HPC compute node provisioning</u></h3>\r
<p><font face="Arial">Microsoft has chosen WDM to provision HPC \r
</u></b></font></li>\r
<li><font face="Arial">WinOF 2.0 is based on<b> (<u>svn.1763 branches\WOF2-0</u>)<br>\r
</b></font></li>\r
- <li><font face="Arial">WinOF 2.1 is based on<b> (<u>svn.2327 branches\WOF2-1</u>)</b></font></li>\r
+ <li><font face="Arial">WinOF 2.1 is based on<b> (<u>svn.2375 branches\WOF2-1</u>)</b></font></li>\r
</ul>\r
<p><a href="#WinOF_Release_Notes"><font color="#000000"><Return-to-Top></font></a></p>\r
<p> </p>\r