[ofw] WinOFED prototype driver for Intel

[Smith, Stan]

From: Barrera, Ivan D
Sent: Thursday, December 05, 2013 9:22 AM
To: Smith, Stan
Subject: RE: WinOFED prototype driver for Intel

Hi Stan,

Thank you for your reply.

What I'm currently trying to do is build the NDv2 provider and its NDFilter driver. MS suggested we could use some of that code as leverage for a prototype driver (again this is the User Mode component (provider) mainly). So I'd like to build this driver so I can start modifying it to use with a protocol driver we currently have.

Sounds like a reasonable plan.
You should really be using the WinOFED 3-2 release source as sadly the mainline trunk was not updated to the 3-2 src level.
Point being a good deal of NDv2 work was done by MS (Microsoft) on behalf of Mellanox and merged into the 3-2 release branch.
See http://www.openfabrics.org/downloads/Windows/v3.2/src/

I was trying to use the "BuildRelease.bat all" script at ofw/gen1/trunk/OFED, but I've noticed some of the batch files here have a check for Win7 as OS. And seems that some of the batch files are intended to build installers (msi) out of binaries.

OK, I now understand your pain. "OFED\buildrelease.bat" is indeed designed to build a 'signed' WinOFED release from the Svr2008 R2 WDK (7600.16385.1) build/nmake env.
Not what you want to use.
I used the win7 7600 WDK environment to generate a DAPL_SA installer (.msi) which worked for Svr2012 R2 sans the WIN8 OS ID.
As the WinOFED project faded away, the need to build via VS10.. and for win8 never came about; so the project remains at win7.
Later this year I will need to migrate the DAPL_SA code base to VS and win8/9.

What I did to build WinOFED 3.2 without installer generation.
>From a cmd.exe window: setenv.bat %systemdrive%\WinDDK\7600.16385.1 fre x64 WIN7 nooacr
Cd to top of your WinOFED tree
build /wgcf

Now that you say WinOF is dead, then I'm wondering what would happen for the win8 support. And I guess this means that the NDv2 provider is for Win2008R2 only.
I guess this is fine, but then does it mean that in order to compile the provider (gen1\trunk\hw\mlx4\user\nd\) and the filter driver (gen1\trunk\core\ndfltr\kernel\) I would need all the development environment (SDK, WDK, HPC SDK) for Windows 7/2008R2 (7600)?

Correct.
There are MS tools, which likely work better these days, which assist in migrating from a win7 build env to VS and win8.
There are MS folks who have worked on WinOFED, actually did the NDv2 work for Mellanox, which could be available to assist in getting to the win8 build env.
You might drop a note to the WinOFED mail list 'ofw at lists.openfabrics.org' to solicit help without revealing any Intel IP.

Sorry if this is confusing. Let me know if this clarifies anything.

And thanks in advance for your help,

Ivan

NO problems.


From: Smith, Stan
Sent: Wednesday, December 04, 2013 6:34 PM
To: Barrera, Ivan D
Subject: RE: WinOFED prototype driver for Intel

Hello,
  A few points to clarify my confusion.
WinOFED is dead...as the once chair of the OFA Windows Working Group, I can confidently state this.
Why....lack of hardware vendor participation and more importantly the fact Microsoft created their own RDMA api known as NetworkDirect v2.
I believe the driver you should, or possibly are and it's late in the day, be building is a NetworkDirect(v2) provider for your RDMA hardware product.
Intel MPI for Windows has always run over the uDAT/uDAPL API which previously was layered over WinOFED verbs (IBAL and OFED verbs).
Since WinOFED is deprecated, DAPL_SA (DAPL Stand-Along [no WinOFED]) is the replacement.
DAPL_SA provides a uDAT/uDAPL API over NetworkDirect(v2).
Hardware vendors (IHVs) supply a WHQL'ed + ND Logo'ed NDv2 provider driver for their respective hardware.
DAPL_SA can utilize any of these ND providers.
To date, the Mellanox Infiniband NDv2 provider is what is used by DAPL_SA and Intel MPI for Windows.
To install Intel MPI for Windows, one downloads the Mellanox WinOF release 4.40 for windows (contains their NDv2 driver), download and install DAPL_SA, install Intel MPI and enjoy MPI on your Win7/Svr2008 R2 or Win8/Svr2012 R2 server.
Should you provide a NDv2 provider for your hardware, then DAPL_SA and Intel MPI should be able to run unmodified over your hardware.

You understand my confusion at this point?

W.r.t. WinOFED batch scripts, which one(s) are you attempting to use?

Stan.

From: Barrera, Ivan D
Sent: Wednesday, December 04, 2013 4:51 PM
To: Smith, Stan
Subject: WinOFED prototype driver for Intel

Hi Stan,

My name is Ivan Barrera, I work for the Networking Division.
I'm starting to write a prototype driver based on the WinOFED for an RDMA product we are designing and I saw your name.
I've been having some issues when I run the batch files, and I was wondering if you have any pointers.

For some reason, despite of including Network Direct v2, I still get messages that I need WDK 7600 as if these files were for Win7 or WinServer 2008 R2.

I would greatly appreciate it if you have any information that can help me to compile this driver for Win8 (or WinServer 2012).

Thanks in advance and sorry to bother you with this.

Ivan Barrera

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20131205/af331ad9/attachment.html>