<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Barrera, Ivan D
<br>
<b>Sent:</b> Thursday, December 05, 2013 9:22 AM<br>
<b>To:</b> Smith, Stan<br>
<b>Subject:</b> RE: WinOFED prototype driver for Intel<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D">Hi Stan,</span></a><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for your reply.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Sounds like a reasonable plan.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">See http://www.openfabrics.org/downloads/Windows/v3.2/src/<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">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.<br>
Not what you want to use.<br>
I used the win7 7600 WDK environment to generate a DAPL_SA installer (.msi) which worked for Svr2012 R2 sans the WIN8 OS ID.<o:p></o:p></p>
<p class="MsoNormal">As the WinOFED project faded away, the need to build via VS10.. and for win8 never came about; so the project remains at win7.<br>
Later this year I will need to migrate the DAPL_SA code base to VS and win8/9.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">What I did to build WinOFED 3.2 without installer generation.<o:p></o:p></p>
<p class="MsoNormal">From a cmd.exe window: setenv.bat %systemdrive%\WinDDK\7600.16385.1 fre x64 WIN7 nooacr<o:p></o:p></p>
<p class="MsoNormal">Cd to top of your WinOFED tree<o:p></o:p></p>
<p class="MsoNormal">build /wgcf<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I guess this is fine, but then does it mean that in order to compile the provider (</span><span style="color:black">gen1\trunk\hw\mlx4\user\nd\)</span><span style="color:#1F497D"> and the filter driver (</span><span style="color:black">gen1\trunk\core\ndfltr\kernel\)</span><span style="color:#1F497D">
I would need all the development environment (SDK, WDK, HPC SDK) for Windows 7/2008R2 (7600)?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Correct.<o:p></o:p></p>
<p class="MsoNormal">There are MS tools, which likely work better these days, which assist in migrating from a win7 build env to VS and win8.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">You might drop a note to the WinOFED mail list ‘ofw@lists.openfabrics.org’ to solicit help without revealing any Intel IP.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Sorry if this is confusing. Let me know if this clarifies anything.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">And thanks in advance for your help,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Ivan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">NO problems.<span style="color:#1F497D"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Smith, Stan <br>
<b>Sent:</b> Wednesday, December 04, 2013 6:34 PM<br>
<b>To:</b> Barrera, Ivan D<br>
<b>Subject:</b> RE: WinOFED prototype driver for Intel<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hello,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> A few points to clarify my confusion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">WinOFED is dead…as the once chair of the OFA Windows Working Group, I can confidently state this.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Why….lack of hardware vendor participation and more importantly the fact Microsoft created their own RDMA api known as NetworkDirect v2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Intel MPI for Windows has always run over the uDAT/uDAPL API which previously was layered over WinOFED verbs (IBAL and OFED verbs).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Since WinOFED is deprecated, DAPL_SA (DAPL Stand-Along [no WinOFED]) is the replacement.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">DAPL_SA provides a uDAT/uDAPL API over NetworkDirect(v2).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Hardware vendors (IHVs) supply a WHQL’ed + ND Logo’ed NDv2 provider driver for their respective hardware.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">DAPL_SA can utilize any of these ND providers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">To date, the Mellanox Infiniband NDv2 provider is what is used by DAPL_SA and Intel MPI for Windows.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Should you provide a NDv2 provider for your hardware, then DAPL_SA and Intel MPI should be able to run unmodified over your hardware.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">You understand my confusion at this point?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">W.r.t. WinOFED batch scripts, which one(s) are you attempting to use?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Stan.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Barrera, Ivan D
<br>
<b>Sent:</b> Wednesday, December 04, 2013 4:51 PM<br>
<b>To:</b> Smith, Stan<br>
<b>Subject:</b> WinOFED prototype driver for Intel<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Stan,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My name is Ivan Barrera, I work for the Networking Division.
<o:p></o:p></p>
<p class="MsoNormal">I’m starting to write a prototype driver based on the WinOFED for an RDMA product we are designing and I saw your name.<o:p></o:p></p>
<p class="MsoNormal">I’ve been having some issues when I run the batch files, and I was wondering if you have any pointers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I would greatly appreciate it if you have any information that can help me to compile this driver for Win8 (or WinServer 2012).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks in advance and sorry to bother you with this.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ivan Barrera<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>