From: Stan Smith Date: Thu, 9 Sep 2010 18:55:17 +0000 (+0000) Subject: [OFED] winOFED 2.3 RC1 X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=8ba75aa8f9ab39e5267a6f45722c0b32987b4760;p=~shefty%2Frdma-win.git [OFED] winOFED 2.3 RC1 git-svn-id: svn://openib.tc.cornell.edu/gen1@2909 ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86 --- diff --git a/branches/WOF2-3/OFED/BuildRelease.bat b/branches/WOF2-3/OFED/BuildRelease.bat index ee1d2ff4..388be33c 100644 --- a/branches/WOF2-3/OFED/BuildRelease.bat +++ b/branches/WOF2-3/OFED/BuildRelease.bat @@ -28,7 +28,7 @@ rem versions. The problem arises when a compile is forced on one folder or the rem other, all instances of ipoib.sys are deleted rem WIX Installer files (.msi) destination folder - set for local environment. -set IDIR=%SystemRoot%\temp +set IDIR=%SystemRoot%\temp\winOFED2-3 if "%1" == "" goto usage if "%1" == "/?" goto usage @@ -227,8 +227,8 @@ if NOT EXIST %ND_SDK_PATH% ( rem set this to be the current svn commit number; overrides svn in path rem processing. Additionally if set to 'latest' code expects ..\..\..\latest.txt rem to contain the SVN number to use. -rem set USE_SVN=1748 -set USE_SVN=latest +rem set USE_SVN=latest +set USE_SVN=2909 rem %2 can be either a file spec or IPENIB_REV value. rem Based on %1 command, FPATH will/will-not be set to a file spec. diff --git a/branches/WOF2-3/OFED/WIX/README.txt b/branches/WOF2-3/OFED/WIX/README.txt index c0dd742e..97d7d841 100644 --- a/branches/WOF2-3/OFED/WIX/README.txt +++ b/branches/WOF2-3/OFED/WIX/README.txt @@ -1,6 +1,6 @@ -[01-28-10] +[09-08-10] -How to generate a Windows OpenFabrics Enterprise Distribution Release (OFED) +How to generate a OpenFabrics Enterprise Distribution for Windows Release (winOFED) using the WIX 3.0 open source installer tool set (http://sourceforge.net/projects/wix/ ). @@ -18,16 +18,17 @@ WinOF Revisions: (based on) 2.0 svn.1763 2.0.2 svn.1975 2.1 svn.2476 - 2.2 svn.2655 -WinOF renamed to OFED + 2.2 svn.2739 + 2.2.1 svn.2778 +WinOF renamed to winOFED 2.3 svn.xxxx Creating a binary release tree ------------------------------ -As of WinOF 2.0 release [Aug'2008] the build environment has been switched over -to Microsoft's WDK (Windows Driver Kit) version 6001.180001. +As of WinOF 2.1 release [Aug'2008] the build environment has been switched over +to Microsoft's WDK (Windows Driver Kit) version C:\WinDDK\7600.16385.0. See gen1\trunk\OFED\BuildRelease.bat file to generate a Wix installer (.msi file) containing signed driver files. diff --git a/branches/WOF2-3/OFED/WIX/README_release.txt b/branches/WOF2-3/OFED/WIX/README_release.txt index 46ce52db..a08b36cf 100644 --- a/branches/WOF2-3/OFED/WIX/README_release.txt +++ b/branches/WOF2-3/OFED/WIX/README_release.txt @@ -1,7 +1,7 @@ -[01-15-10] OFED 2.2 RC2 Release available +[09-09-10] OFED 2.3 RC1 Release available -Release available @ http://www.openfabrics.org/downloads/OFED/v2.3_RC0 +Release available @ http://www.openfabrics.org/downloads/windows/v2.3_RC1 Please address comments and concerns to https://bugs.openfabrics.org and/or the Windows OpenFabrics email list ofw@lists.openfabrics.org @@ -10,47 +10,53 @@ Windows OpenFabrics email list ofw@lists.openfabrics.org OFED Release Summary ----------------- -1) The OFED 2.2 release is based on openib-windows source svn revision - (branches\OFED2-2 svn.2667). +1) The OFED 2.3 release is based on openib-windows source svn revision + (branches\WOF2-3 svn.2909). - Last OFED release (2.1) based on svn.2476. + Last OFED release (2.2) based on svn.2739. -2) Features +2) New Features - Installers available for Windows 7 & Server 2008 R2 + uDAT / uDAPL 2.0.30 code base: + 32-bit providers available. + UCM (Unreliable Datagram Connection Manager) DAPL provider available. - NDIS 6 IPoIB for Server 2008, Svr 2008 R2, Windows 7 and Vista. + OpenSM upgraded to version 3.3.6 (see %windir%\temp\osm.log for SM details). - NDIS 5.1 IPoIB for Server 2003 & XP. - - uDAPL 2.0.25 code base: - No longer supporting uDAT/uDAPL version 1.0, uDAT/uDAPL version 2.0 only. - - OpenSM upgraded to version 3.3.3 (see %windir%\temp\osm.log for SM details). - - OFED installer upgraded to WIX 3.0 - - ND/winverbs provider available as a technology preview (see ndinstall -h). + OFED (Open Fabrics Enterprise Distribution) verbs API documented in manual.htm 2) Bug fixes in IB Core + cl_timer race conditions fixed + ibal memory leaks fixed. + IPoIB - WSD - DAT/DAPL + DHCP is now working correctly in larger HPC Edition clusters. + DHCP correctly inter-operating with Linux. + DPC threads replaced with IO work queue threads to allow system scheduling fairness. + WinVerbs + Overlap structures initialized correctly. + WinMAD - OFED (Open Fabrics Enterprise Distribution [Linux]) verbs API + ReadFile/WriteFile return values checked. + + OFED (Open Fabrics Enterprise Distribution) verbs API IPoIB - SRP + NetworkDirect providers: IBAL & winverbs + Memory leaks fixed. + OFED Installer - manual + Winverbs, winmad, dat/dapl .dlls installed into %windir%\system32\ + For 64-bit architectures, 32-bit .dll versions are installed into %windir%\SysWow64\ + **** Known Issues **** HCA drivers are reclassified as BOOT_START drivers to support booting from -an SRP IOC. An unfortunate side-effect is when OFED 2.2 is installed +an SRP IOC. An unfortunate side-effect is when OFED 2.3 is installed on a system for the first time, after installation a mandatory reboot is Required by Windows. @@ -79,4 +85,4 @@ Please: Thank you, -OFED for Windows Developers. +OFED for Windows developers. diff --git a/branches/WOF2-3/OFED/WIX/Release_notes.htm b/branches/WOF2-3/OFED/WIX/Release_notes.htm index 7ad59495..9be9f25a 100644 --- a/branches/WOF2-3/OFED/WIX/Release_notes.htm +++ b/branches/WOF2-3/OFED/WIX/Release_notes.htm @@ -87,12 +87,13 @@ ul

-

Windows OpenFabrics

+

OpenFabrics Enterprise Distribution +for Windows

-

2.2 Release Notes

+

2.3 Release Notes

-01/13/2010

+09/09/2010
@@ -130,7 +131,7 @@ Trouble Shooting

Local Network Adapter Ordering

-Which WinOF release is installed?

+Which release is installed?

QLogic VNIC Configuration

@@ -146,36 +147,35 @@ Known Issues

Overview

-

The -Windows OpenFabrics (WinOF) release package is composed of software modules -intended for use on Microsoft Windows based computer systems connected via an -InfiniBand fabric.

+

The OpenFabrics +Enterprise Distribution release package is composed of software modules +intended for use on Microsoft Windows based computer systems connected via an InfiniBand fabric.

 Binary files generated from the OpenIB-windows developers subversion (svn) source tree 'svn://openib.tc.cornell.edu' -(branches\WOF2-2 svn revision 2667) +(branches\OFED2-3 svn revision 2909 are packaged into a WIX -(Windows Installer Xml) single file install package referred to as the -Windows OpenFabrics (WinOF) release 2.2.
+(Windows Installer Xml) single file install package referred to as the OpenFabrics Enterprise +Distribution for Windows release 2.3.

 

-This WinOF 2.2 is a full release as it contains:

+This OFED 2.3 is a full release as it contains:

-

The Windows OpenFabrics (WinOF) release package contains the following:
+

The OpenFabrics Enterprise Distribtuion for Windows (OFED-W) release package contains the following:

OpenFabrics InfiniBand core drivers and Upper Level Protocols (ULPs):

    @@ -243,8 +243,9 @@ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none;

    Performance tests

  • -

    - OFED Diagnostics

    +

    + + Diagnostic tools

@@ -288,7 +289,7 @@ style='background-position: 0% 0%; mso-highlight:yellow; background-image:none;
  • Windows - Server 2008 R2 + HPC SP2

    + Server 2008 R2 HPC Edition

  • Windows 7

    @@ -319,6 +320,31 @@ Mellanox Firmware (FW) versions and update tools

    Current HCA firmware version can be viewed from the 'vstat' command or the Mellanox firmware tool flint.

    +

    How to +find the PSID of a Mellanox HCA

    +
    +

    Should the OFED stack not install; possibly due to outdated + firmware:
    +
    + Download and install the Mellanox Firmware burning tools from + + Mellanox Support

    +

    After you determine the PSID,
    +
    + Download Mx Firmware image .zip file from + + Mellanox Firmware download

    +

    How to find the PSID of the Mellanox card if the OFED stack did not install, + otherwise use vstat.
    +
    + mst status
    + Found 2 devices:
    + mt26418_pciconf0
    + mt26418_pci_cr0
    +
    + flint -d mt26418_pci_cr0 query
    + In the output, you will find the PSID.

    +

    Supported Switches

    @@ -350,16 +376,16 @@ Mellanox firmware tool flint.

    Notes

    User mode tools and diagnostics are installed in '%SystemDrive%\Program -Files\WinOF'.  Although device driver modules initially reside in -'%SystemDrive%\Program Files\WinOF\Drivers', when installed the Windows device +Files\OFED'.  Although device driver modules initially reside in +'%SystemDrive%\Program Files\OFED\Drivers', when installed the Windows device installer copies driver files to %SystemRoot%\system32 & %SystemRoot%\SysWOW64'. DAT & DAPL runtime libraries are installed into %SystemRoot% in order to be accessible by user mode applications.
    -WinOF user mode executables are designed to be run from -a Command Prompt window; see  'Start->Program Files-> Windows OpenFabrics-> Command Prompt'.

    -

    '%SystemDrive%\Program Files\WinOF' is appended to the system wide search +OFED user mode executables are designed to be run from a Command Prompt window; +see  'Start->Program Files->OpenFabrics Enterprise Distribution-> OFED-> Command Prompt'.

    +

    '%SystemDrive%\Program Files\OFED' is appended to the system wide search path environment variable 'PATH'; any command windows created after the installation will have the updated -%PATH% environment variable, hence will be able to access WinOF executables.

    +%PATH% environment variable, hence will be able to access OFED executables.

    The ‘default’ installation installs ‘released/free’ (not checked/debug) versions of drivers and executables. Debug/Checked versions are @@ -367,22 +393,22 @@ available as an install feature.

    A single instance of a subnet manager, opensm.exe, must be running on a fabric connected node in order for the Infiniband fabric to be -configured and useful; either Windows or Linux OFED opensm work well.

    +configured and useful; either Windows or Linux versions of openSM work well.

    It is recommended that OpenSM be run as a Windows service.  A typical -WinOF install will install OpenSM as a Windows service which +OFED install will install OpenSM as a Windows service which is disabled; after an installation, choose your openSM node and start the openSM service.  -See the WinOF Manual for details on opensm as a service.
    +See the OFED Manual for details on opensm as a service.
    By selecting the 'OpenSM_Service_Started' install feature, a local OpenSM subnet management service will be automatically started.

    Note, the opensm.exe process must continue to run in order -to maintain Infiniband fabric configuration. Should the opensm.exe process die, +to maintain an Infiniband fabric configuration. Should the opensm.exe process die, restart the service if not automatic or re-run opensm.exe in order to continue correct fabric operation.

    For more subnet management information, consult the Windows -OpenFabrics manual.

    +OpenFabrics Enterprise Distribution manual.

    <Return-to-Top>

    @@ -396,7 +422,7 @@ OpenFabrics manual.

  • Double-click the .msi installer file, Except for Vista.
  • For Vista installs, from an privileged administrator command window, execute 'msiexec /I - WinOF_2-2_wlh_xxx.msi'.
  • + OFED_2-2_wlh_xxx.msi'.

    Requirements

    @@ -405,14 +431,15 @@ package. Upon reboot, cancel any attempts to install new device hardware from the "Found New Hardware Wizard".

    If you have previously installed openib-windows, WinOF (Windows OpenFabrics) -packages or vendor supplied Infiniband packages, uninstall and reboot prior to -installing this version of Windows OpenFabrics (WinOF).

    +packages or vendor supplied Infiniband packages, uninstall and reboot prior to +installing this version of OpenFabrics Enterprise Distribution for Windows.

    -

    For an existing Windows OpenFabrics (WinOF) uninstall
    -    Start-> Programs-> Windows OpenFabrics-> Uninstall WinOF
    +

    For an existing Windows OpenFabrics Enterprise +Distribution (OFED) uninstall
    +    Start-> Programs-> OpenFabrics Enterprise Distribution-> Uninstall OFED
          -or-
    -    Control Panel -> Add or Remove Programs-> Windows -OpenFabrics->Remove.

    +    Control Panel -> Add or Remove Programs->OpenFabrics +Enterprise Distribution->Remove.

    openib-windows (IB stack before WinOF 1.0 release) uninstall: (not the normal uninstall case)

    @@ -442,15 +469,18 @@ drivers for newly discovered PCI device (HCA).

    Vista installation only; open a privileged Administrator command window and type

    -

        start/wait msiexec /I WinOF_2-1_wlh_xxx.msi

    +

        start/wait msiexec /I OFED_2-1_wlh_xxx.msi

    For all other Windows variants, double-clicking the installer file (.msi) -works correctly to start a WinOF installation.
    -From a login session with administrator privileges, File Explorer view, double-click the WinOF_M-m{-p}_OSE_arch.msi file to begin the Windows OpenFabrics +works correctly to start an OFED installation.
    +From a login session with administrator privileges, File Explorer view, double-click the OFED_M-m{-p}_OSE_arch.msi file to begin the Windows OpenFabrics +Enterprise Distribution installation.

    Where 'M-n{-p}' indicates Major release number, Minor release number, and optional point-release number.

     OSE - Operating System Environment:

    Correct Installation Validation

    From the Device Manager you should find the following devices:

    @@ -1116,12 +1166,12 @@ mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">
  • From a command window type 'devmgmt.msc'
  • InfiniBand Host Channel Adapters -> InfiniHost or Mellanox ConnectX
  • The System Devices -> InfiniBand Fabric device is no longer present in - WinOF 2.0 and following releases.
  • + OFED 2.0 and following releases.
  • Network Adapters -> OpenIB IPoIB Adapter (an Instance per HCA port).
  • Validation Test

    -

    Open a WinOF command window

    +

    Open a OFED command window

    1. Start->Program Files->Windows OpenFabrics -> Command Window
    2. @@ -1137,7 +1187,7 @@ Window

      Limit the number of Subnet Managers on your fabric; one SM per fabric is sufficient, although redundant Subnet Managers are supported.

        -
      1. After a 'typical' WinOF install, OpenSM is installed as a disabled +
      2. After a 'typical' OFED install, OpenSM is installed as a disabled Windows service named "InfiniBand Subnet Management".
        To start the OpenSM service, from a command window type 'services.msc' to start the Services manager.  From the Services manager, find and select @@ -1167,18 +1217,18 @@ check for your desired adapter ordering.

        <Return-to-Top>

         

        -

        Which WinOF release is installed?

        +

        Which OFED release is installed?

        1. Control Pannel -->Add/Remove Programs or  - -->Programs/Features entry identifies the installed WinOF release version.
        2. + -->Programs/Features entry identifies the installed OFED release version.
        3. Start->Programs->Windows OpenFabrics (check Uninstall entry).
        4. Driver confirmation from the Device Manager:
              Query My Computer-> Manage-> Device Manager-> Network Adapters-> OpenFabrics IPoIB Adapter-> Properties-> Driver-> Details
              The subversion (svn) revision number will be listed under 'Driver Version'. The svn revision number will match what's listed in the release notes.
        5. -
        6. Hold the mouse point over \Program Files\WinOF\ib_read_bw.exe to display -the file version; [WinOF-Major.Minor.not-used.svn revision number].
        7. +
        8. Hold the mouse point over \Program Files\OFED\ib_read_bw.exe to display +the file version; [OFED-Major.Minor.not-used.svn revision number].
        • WinOF 1.0 is based on openib-windows svn revision 614 @ @@ -1193,7 +1243,9 @@ the file version; [WinOF-Major.Minor.not-used.svn revision number].
        •  
        • WinOF 2.1 is based on (svn.2476 branches\WOF2-1)
           
        • -
        • WinOF 2.2 is based on (svn.2667 branches\WOF2-2)
        • +
        • WinOF 2.2 is based on (svn.2667 branches\WOF2-2)
        • +
        • OFED 2.3 is based on (svn.2909 branches\WOF2-3)

        <Return-to-Top>

         

        @@ -1285,7 +1337,7 @@ for the setting to take effect.

        In order for DAT/DAPL programs to execute correctly, the 'dat.dll' file must be present in the current directory, %SystemRoot% or in the library search path.

        -

        WinOF installation places the dat2.dll and dapl2.dll +

        OFED installation places the dat2.dll and dapl2.dll files in the '%SystemRoot%' folder (a.k.a. \Windows).

        The DAT/DAPL configuration file by convention is defined as @@ -1293,7 +1345,7 @@ folder (a.k.a. \Windows).

        a template configuration file will be installed as '%SystemDrive%\DAT\dat.conf'.
        In order to preserve existing installations, the dat.conf file is not automatically installed if '%SystemDrive%\DAT\dat.conf' exists.
        -A sample dat.conf file is always installed as '\Program Files\WinOF\dat.conf +A sample dat.conf file is always installed as '\Program Files\OFED\dat.conf '.

        The default DAT configuration file specification can be overridden by use of the environment variable DAT_OVERRIDE. Such that 'DAT_OVERRIDE=D:\MyDAT\test.conf' @@ -1307,7 +1359,7 @@ library file specification must be contained within double-quotes. A side effect of the double-quotes is the library specification is treated as a Windows string which implies the '\' (backslash character) is treated as an 'escape' character.  Hence all backslashes in the library path must be duplicated when enclosed in -double-quotes (e.g., "C:\\Programs Files\\WinOF\\dapl.dll").

        +double-quotes (e.g., "C:\\Programs Files\\OFED\\dapl.dll").

        uDAT/uDAPL version 2.0 runtime libraries are identified as dat2.dll and dapl2.dll, both in %SystemRoot%; see manual for further details.
        @@ -1319,13 +1371,13 @@ no longer available as support for v1.1 is deprecated.

         

        SRP (SCSI RDMA Protocol) Driver Installation

        -

        The WinOF installer does not install the SRP driver as part of a default +

        The OFED installer does not install the SRP driver as part of a default installation.  If the SRP feature is selected in the custom installation window, an InfiniBand SRP Miniport driver will be installed; see the device manager view under SCSI and RAID controllers.

        The system device 'InfiniBand I/O Unit' (IOU) -device is required for correct SRP operation.  The WinOF installer will +device is required for correct SRP operation.  The OFED installer will install/load the IOU driver if the SRP feature is selected.  See the device manager view System Devices --> InfiniBand I/O Unit for conformation of correct IOU driver loading.

        @@ -1337,7 +1389,7 @@ When the subnet manager communicates the existence of an SRP target, Windows PNP then will load the IBiou.sys driver along with the ib_srp.sys driver.

        An invocation of 'diskmgmt.msc' will display available SRP target disks.

        -

        Consult the WinOF manual for further SRP +

        Consult the OFED manual for further SRP topics including configuring a Linux OFED SRP target.

        SRP Driver Uninstall

        If the SRP (SCSI RDMA Protocol) driver has been previously @@ -1360,9 +1412,9 @@ valid for diskpart (ver 6.0.6001) which is not distributed with Windows Server Letter.

      3. The consequences of not releasing the SRP target drive(s) are that after the -WinOF uninstall reboot there are lingering InfiniBand driver files. These driver +OFED uninstall reboot there are lingering InfiniBand driver files. These driver files remain because while the SRP target is active they have references, thus -when the WinOF uninstall attempts to delete the files the operation fails.

        +when the OFED uninstall attempts to delete the files the operation fails.


        <Return-to-Top>

        @@ -1386,11 +1438,11 @@ WinVerbs.dll and libibmad.dll userspace libraries install as part of the Winverbs driver installation package.
        Additionally, a Windows port of the OFED libibverbs library, several test programs and OFED InfiniBand diagnostic utilities are also included.

        -

        As of WinOF 2.1, Winverbs components are now integral -components of a default WinOF installation.
        +

        As of OFED 2.1, Winverbs components are now integral +components of a default OFED installation.
        Although WinVerbs, WinMAD drivers, OFED libraries and utilities are install selectable features, they are automatically included as part of the default -WinOF install.

        +OFED install.

        @@ -1399,14 +1451,20 @@ WinOF install.

        <Return-to-Top>
         

        -

        Known Issues
         

        - +

        Known Issues

          +
        • +

          Should the OFED stack not + install with a notifier "Possible HCA driver install failure", the likely + cause is outdated HCA firmware.
          + See finding the PSID + text for firmware burning instructions.

        • HCA drivers are now classified as 'BOOT START' drivers; the implication being for a first time - install, the system will reboot after installation.

        • + install, the system will reboot after installation.
           

          +
        • IPoIB partition multicast @@ -1448,7 +1506,8 @@ WinOF install.

          adapter"  igmpprototype=igmprtrv2

           

          -

          Future WinOF releases +

          Future + OFED releases will support IGMP V3.

           

        • diff --git a/branches/WOF2-3/OFED/WIX/common/Config.inc b/branches/WOF2-3/OFED/WIX/common/Config.inc index 1b7db20f..ea62a8a3 100644 --- a/branches/WOF2-3/OFED/WIX/common/Config.inc +++ b/branches/WOF2-3/OFED/WIX/common/Config.inc @@ -1,7 +1,7 @@ - +