[ofw] OFED for Windows 3.0 RC2 release is available for download
Fab Tillier
ftillier at microsoft.com
Thu Nov 10 10:00:44 PST 2011
Hi Stan,
Smith, Stan wrote on Thu, 10 Nov 2011 at 08:54:31
>> From: Fab Tillier
>> Sent: Wednesday, November 09, 2011 7:45 PM
>>
>> Hi Stan,
>>
>> For the rename of complibd to complib, did we solve the ABI issue?
>> That is, do we have anything that prevents/catches someone that mixes
>> release bits of say IBAL, and a debug version of complib? The
>> quicklist stuff will most likely break, because the list item is
>> different between debug and release.
>>
>> -Fab
>
> Hi,
> Uri did the conversion work which I reviewed/tested. I did not see any
> explicit tests which would identify a free/checked mismatch.
> Holding the mouse-point over the file in question eventually will pop a file
> attributes display, with 'some' files identifying a 'DEBUG' version (e.g.,
> checked ipoib.sys); all driven by the .rc file definition.
> I had requested Uri to update all the .rc files for which he was removing the
> 'd' suffix from the linked file, to identify DEBUG versions. Uri declined stating
> it was too much work which he had no time for.
What a load of bull, how long does it take to change the .rc files, using an existing .rc (e.g. from ipoib) as an example? 5 minutes? This is just another example of how WinOF is treated as a dumping ground/out house by Mellanox. Seriously, WTF.
> There was some original work in numerous .rc files using 'ifdef _DEBUG_'
> which no longer works; sadly the case in point for complib.dll, hence a
> checked complib.dll does not show the DEBUG attribute.
> For ipoib.sys I replaced _DEBUG_ with the MS predefined 'DBG'.
> I'll look into it for RC3.
> Are you seeing mismatches?
I originally added the 'd' suffix because of mismatches. Without them, you must always run a homogeneous stack, so you can't debug an app without flipping everything to debug. If you flip the whole stack, you must also flip any applications that might have a dependency.
I would suggest rolling back the change for RC3, and just not shipping the debug bits - only install the release bits, and provide a zip file with the debug DLLs to facilitate development (do we have an SDK package)?
Alternatively, maybe only complib has the problem - I haven't checked to see if IBAL, WinVerbs, etc. have ABI issues with structures changing sizes between release and debug builds. If complib is the only one, we might be better off making it a static library rather than a DLL, and avoid the whole problem that way.
Cheers,
-Fab
>
> Stan.
>>
>> -----Original Message----- From: ofw-bounces at lists.openfabrics.org
>> [mailto:ofw- bounces at lists.openfabrics.org] On Behalf Of Smith, Stan
>> Sent: Wednesday, November 09, 2011 5:38 PM To: ofw_list Subject: [ofw]
>> OFED for Windows 3.0 RC2 release is available for download
>>
>> OFED for Windows 3.0 RC2 release is available for download @
>> http://www.openfabrics.org/downloads/Windows/v3.0_RC2
>> Please address comments and concerns to https://bugs.openfabrics.org
>> and/or the OFED for Windows email list ofw at lists.openfabrics.org
>>
>>
>> Changes since winOFED 3.0 RC1 release
>> -------------------------------------
>>
>> 1) DAPL updated to 2.0.34
>>
>> 2) 'About OFED' added to the start menu under 'OpenFabrics Enterprise
> Distribution'.
>>
>>
>> [10-28-11] winOFED 3.0 RC1 svn.3331 released.
>>
>>
>> OFED for windows Release Summary
>> --------------------------------
>>
>> 1) The winOFED 3.0 release is based on openib-windows source svn revision
> #3342
>> (branches\WOF3-0).
>>
>> Last OFED release (2.3) based on svn.3041.
>> 2) New Features or Changes:
>>
>> Windows Server 2003 and Windows XP environments are no longer
> supported.
>>
>> Device drivers and installer .msi files are signed with a new OpenFabrics
>> Alliance digital-ID certificate.
>>
>> You will be asked if you trust the OpenFabrics Alliance as a
>> Software publisher, answer 'yes' to continue the installation.
>>
>> uDAT / uDAPL 2.0.35 code base
>>
>> OpenSM upgraded to version 3.3.11 (see '%windir%\temp\osm.log' for
> runtime SM details).
>>
>> IB Diags upgraded to 1.5.9 version.
>>
>> IPoIB CM (Connected Mode) is supported; default mode is UD.
>> See IPoIB instance (devmgmt.msc) properties->Advanced tab to
>> enable CM mode. Once CM mode is enabled, check MTU size with
>> 'netsh int ip show int'. reset MTU size with 'netsh int ip set
>> interface device-index mtu=new-
> mtu-value'.
>> Find device-index via 'netsh int ip show int', match connected Local Area
> Connection.
>> A single 'ttcp -b 256K' stream should demonstrate 400+ MB/sec data
> rates for IPoIB CM.
>>
>> Debug file/executable versions no longer have a 'd' appended to the
> filename
>> example: complibd.dll --> complib.dll
>> An IBAL thread no longer rescans for IOC/IOU changes at 30 second
> intervals.
>> New default behavior is to IOC rescan on demand (IB Port Active
>> transition, device rescan via devmgmt.msc->Scan for hardware
>> changes) or (%ProgramFiles%\OFED\drivers\devman.exe rescan).
>>
>> diskmgmt.msc->Rescan disks will not see new SRP targets until a
>> 'device' rescan has finished (devmgmt.msc->Scan for hardware
>> changes).
>>
>> Registry entry IocPollInterval controls IOC rescan behavior:
>> 0 = No IOC rescanning.
>> 1 = IOC rescan on demand ('devman rescan' or IB port Active state
> transition).
>>> 1 = IOC rescan every 'IocPollInterval' milliseconds; previous value was
> 30000
>>
>> Start menu 'OpenFabrics Enterprise Distribution' list now contains an
> 'About OFED' selection.
>>
>> 2) Bug fixes - all components.
>>
>> 3) RoCE hardware not supported at this time.
>>
>>
>> **** Known Issues ****
>>
>> IB cable disconnect during ND v1 transfer will crash system (winverbs
>> problem).
>>
>> Disabling the HCA on a system while openSM is running will crash the
>> system (winmad issue).
>>
>> HCA drivers are reclassified as BOOT_START drivers to support booting from
>> an SRP IOC. An unfortunate side-effect is when OFED 3.0 is installed
>> on a system for the first time, after installation a mandatory reboot is
>> Required by Windows.
>>
>> If the install appears to hang, look around for popup windows
>> requesting input which are covered by other windows. Such is the case
>> on Server 2008 initial install - Answer 'yes' to always trust the
>> OpenFabrics Alliance as a SW publisher.
>>
>>
>> Please:
>> Read the Release_notes.htm file!
>>
>> make 'sure' your HCA firmware is recent:
>> vstat.exe displays HCA firmware version & PSID.
>> flint.exe (found at the Mellanox website, Windows firmware tools
> download package) displays PSID.
>>
>> Thank you,
>>
>> OFED for Windows developers.
>>
>>
>> _______________________________________________
>> ofw mailing list
>> ofw at lists.openfabrics.org
>> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
More information about the ofw
mailing list