<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:"Intel Clear";}
/* 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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Intel Clear";
color:#44546A;
font-weight:normal;
font-style:normal;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{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">Hi Ray,<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">We strongly prefer Options #2. We think it is important to continue supporting OFA official releases for some time to come. We also don’t think it makes sense to release what is in the trunk today as a 2015
release and then follow up almost immediately on its heels with a 2016 release containing all the patches below. Hence our vote for Option #2.
<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">Samsung is very comfortable in committing to delivering the 3 patches below in the Option #2 timeframe.<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">In fact, we will be ready with our first patch(PerfOpts + 2 critical bug fixes – see below) after 5 days of pushing the Namespace management patch to main branch.<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">In addition to PerfOpts support, we will be including two critical bug fixes in our first patch – both fixes for BSODs:<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">1. The first bug fix addresses the following:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">There is a basic race condition/synchronization issue in the driver which allows the Admin queue’s
</span><span style="color:#1F497D">linked list of cmd_entry structures (pSQI->FreeQList) to get corrupted. In the current code, this list can be manipulated by different processors concurrently. When that happens, a BSOD (“A LIST_ENTRY has been corrupted (i.e.
double remove)”) occurs</span><span style="color:black">.</span><span style="color:#1F497D"> This hole is fixed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">2. The second bug fix addresses the following:
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">If a new SRB that comes in while a Format NVM is in progress, the NVMeBuildIo looks at the SCSI CDB opcode and rejects reads/writes.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">The code that does this checking needs to make sure the request coming in is a SCSI-CDB based request before it tries to look at the CDB opcode - but it does not. The logic is in the
wrong place in NVMeBuildIo. The current code results in an attempt to access a null pointer and BSODs.</span><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Judy<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<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"">
<a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a>
<a href="mailto:[mailto:nvmewin-bounces@lists.openfabrics.org]">[mailto:nvmewin-bounces@lists.openfabrics.org]</a>
<b>On Behalf Of </b>Robles, Raymond C<br>
<b>Sent:</b> Thursday, January 14, 2016 3:55 PM<br>
<b>To:</b> 'nvmewin@lists.openfabrics.org'<br>
<b>Subject:</b> [nvmewin] Happy New Year... and status update<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Hello and Happy New Year,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">I hope everyone had a great holiday season and is off to a great start to the new year!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">As communicated last month, the patch from HGST for the SCSI multi-initiator changes has been approved and pushed. The holidays slowed down much of the progress on the
OFA driver and there were several patches that did not get pushed prior to the end of the year. The list of patches remained to be pushed are as follows…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:Symbol;color:#44546A">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Namespace Management (Intel)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:Symbol;color:#44546A">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Perf Opts (Samsung)
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:Symbol;color:#44546A">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Win 8.1 Timers (Samsung)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:Symbol;color:#44546A">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">EOL Read Only (Samsung)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:Symbol;color:#44546A">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Concurrent channels (Google)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">The namespace management patch will be sent out for review tomorrow (look for the patch email from Carolyn)… stay tuned!!!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">However, once this patch is resolved, we as a community will have to make a decision on an official release strategy. The patch process and cadence was significantly
slower in 2015 which leaves us with a few options. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Release what is in the trunk today (or after the namespace management patch)… and call that the 2015 release (albeit later than expected)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">In lieu of an official 2015 release, we push the remaining patches listed above… and then release in ~Q2 of 2015. Basically skip a 2015 release and go right into the mid-2016 release.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#44546A">
</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Remove the concept of “official releases” from the OFA Windows NVMe driver and just allow people, companies, and users to pull from the OFA trunk as necessary.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">For #3 above, my thoughts are that because the OFA driver is not a production driver… but a reference and enabling driver, it should/could be managed as just that… a
reference baseline driver that any potential user can go and grab the source, or contribute a patch. Nothing more… nothing less.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A;background:yellow;mso-highlight:yellow">For the release decision, I’ll be happy to call a meeting… but we can also handle it via email as well… just let me know. Feedback
from all is welcome… but I would request mandatory feedback form the 4 reviewing companies: Samsung, HGST, PMC-Sierra, and Intel. How would you like to proceed?</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A">Ray<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Intel Clear";color:#1F497D"><img border="0" width="54" height="39" id="Picture_x0020_1" src="cid:image001.png@01D152CC.1E3B8C00" alt="cid:image001.png@01CB3870.4BB88E70"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><i><span style="font-family:"Intel Clear";color:#1F497D">Raymond C. Robles<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#1F497D">Non-Volatile Memory Solutions Group<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#1F497D">Intel Corporation<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#1F497D">Office: 480-554-2600<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear";color:#1F497D">Mobile: 480-399-0645</span><span style="font-size:10.0pt;font-family:"Intel Clear";color:#44546A"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>