<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]--><title>Samsung Enterprise Portal mySingle</title><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:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
@font-face
{font-family:"Intel Clear";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-believe-normal-left:yes;}
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
{mso-style-priority:99;
margin-top:3.75pt;
margin-right:0in;
margin-bottom:3.75pt;
margin-left:0in;
font-size:9.0pt;
font-family:"Arial","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:8.0pt;
font-family:"Tahoma","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;
font-weight:normal;
font-style:normal;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#44546A;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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 mso 9]><style>p.MsoNormal
{margin-left:7.5pt;}
</style><![endif]><!--[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" style='margin-left:7.5pt;margin-top:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt'><div class=WordSection1><p><b><span style='font-family:"Trebuchet MS","sans-serif";color:#AAAAAA'>Dell - Internal Use - Confidential </span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A'>Dell would also prefer option 2. We like to start with an “official” release that has been through some level of testing and has been WHQL’d and use that as our base. If the official version passes all of our internal validation then we use that as our customer release, else we’ll patch locally for our customer release and push the patches back upstream (fork and merge model). This is what we’ve done for the prior few releases and the model seems to work well.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A'>Austin<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A'><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 style='margin:0in;margin-bottom:.0001pt'><a name="_____replyseparator"></a><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"'> nvmewin-bounces@lists.openfabrics.org [mailto:nvmewin-bounces@lists.openfabrics.org] <b>On Behalf Of </b>Thomas Freeman<br><b>Sent:</b> Wednesday, January 20, 2016 2:50 PM<br><b>To:</b> Robles, Raymond C; suman.p@samsung.com; nvmewin-request@lists.openfabrics.org; nvmewin@lists.openfabrics.org<br><b>Cc:</b> anshul@samsung.com; MANOJ THAPLIYAL; tru.nguyen@ssi.samsung.com<br><b>Subject:</b> Re: [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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ray,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I don’t have a strong opinion toward #3, I’m content with option #2 also.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:90%'><b><span style='font-size:10.0pt;line-height:90%;font-family:"Arial","sans-serif";color:#1F497D'>Tom Freeman</span></b><b><span style='font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></b></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:90%'><b><span style='font-size:10.0pt;line-height:90%;font-family:"Arial","sans-serif";color:#1F497D'>Software Engineer, Device Manager and Driver Development</span></b><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:90%'><span style='font-size:10.0pt;line-height:90%;font-family:"Arial","sans-serif";color:#1F497D'>HGST, a Western Digital company</span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:90%'><span style='font-size:10.0pt;line-height:90%;font-family:"Arial","sans-serif";color:#1F497D'><a href="mailto:thomas.freeman@hgst.com">thomas.freeman@hgst.com</a></span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:90%'><span style='font-size:10.0pt;line-height:90%;font-family:"Arial","sans-serif";color:#1F497D'>507-322-2311<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:90%'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;line-height:90%'><span style='font-size:11.0pt;line-height:90%;font-family:"Calibri","sans-serif";color:#1F497D'><img border=0 width=172 height=56 id="Picture_x0020_1" src="cid:image001.png@01D15394.D39900A0" alt="HGST_Logo_email"><o:p></o:p></span></p><p class=MsoNormal style='line-height:90%'><span style='font-size:8.0pt;line-height:90%;font-family:"Arial","sans-serif";color:#1F497D'>3605 Hwy 52 N </span><span style='color:#1F497D'><br></span><span style='font-size:8.0pt;line-height:90%;font-family:"Arial","sans-serif";color:#1F497D'>Rochester, MN 55901</span><span style='color:#1F497D'><br><a href="https://hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/" target="_blank"><span style='font-size:8.0pt;line-height:90%;font-family:"Arial","sans-serif"'>www.hgst.com</span></a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";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 style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","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> Wednesday, January 20, 2016 2:45 PM<br><b>To:</b> <a href="mailto:suman.p@samsung.com">suman.p@samsung.com</a>; <a href="mailto:nvmewin-request@lists.openfabrics.org">nvmewin-request@lists.openfabrics.org</a>; <a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br><b>Cc:</b> <a href="mailto:anshul@samsung.com">anshul@samsung.com</a>; MANOJ THAPLIYAL <<a href="mailto:m.thapliyal@samsung.com">m.thapliyal@samsung.com</a>>; <a href="mailto:tru.nguyen@ssi.samsung.com">tru.nguyen@ssi.samsung.com</a><br><b>Subject:</b> Re: [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'>Hi Suman/Judy,<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'>Thank you for your response. Right now, the current vote is…<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'>Samsung – Option #2<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Intel Clear";color:#44546A'>HGST – Option #3<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Intel Clear";color:#44546A'>PMC Sierra – TBD<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:#44546A;background:yellow;mso-highlight:yellow'>Alex/Kwok, what is your vote/preference on the release options below.</span></b><b><span style='font-size:10.0pt;font-family:"Intel Clear";color:#44546A'><o:p></o:p></span></b></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><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> SUMAN PRAKASH B <a href="mailto:[mailto:suman.p@samsung.com]">[mailto:suman.p@samsung.com]</a> <br><b>Sent:</b> Wednesday, January 20, 2016 9:10 AM<br><b>To:</b> Robles, Raymond C; <a href="mailto:nvmewin-request@lists.openfabrics.org">nvmewin-request@lists.openfabrics.org</a>; <a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br><b>Cc:</b> <a href="mailto:tru.nguyen@ssi.samsung.com">tru.nguyen@ssi.samsung.com</a>; <a href="mailto:judy.brock@ssi.samsung.com">judy.brock@ssi.samsung.com</a>; MANOJ THAPLIYAL; <a href="mailto:anshul@samsung.com">anshul@samsung.com</a><br><b>Subject:</b> Re: Happy New Year... and status update<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hello Ray,<br><br>Samsung votes for <strong><u><span style='font-family:"Calibri","sans-serif"'>Option #2</span></u></strong>. We push the remaining patches listed and then release in ~Q2 of 2015.</span><o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>And as planned, Samsung will submit the following patches, along with some critical bug fixes.</span><o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>a) Perf Opts (Samsung)<br>b) Win 8.1 Timers (Samsung)<br>c) EOL Read Only (Samsung)</span><o:p></o:p></p><p> <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>And we will be ready with our first patch "Perf Opts" after 5 days of pushing the Namespace management patch to main branch.</span><o:p></o:p></p><p> <o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Please let us know your opinion.</span><o:p></o:p></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><br>Regards,<br>Suman</span><o:p></o:p></p><p><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 19 Jan 2016 14:32:45 +0000<br>From: Judy Brock-SSI <<a href="mailto:judy.brock@ssi.samsung.com">judy.brock@ssi.samsung.com</a>><br>To: "Robles, Raymond C" <<a href="mailto:raymond.c.robles@intel.com">raymond.c.robles@intel.com</a>>,<br> "'nvmewin@lists.openfabrics.org'" <<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>><br>Subject: Re: [nvmewin] Happy New Year... and status update<br>Message-ID:<br> <<a href="mailto:36E8D38D6B771A4BBDB1C0D800158A51865B7376@SSIEXCH-MB3.ssi.samsung.com">36E8D38D6B771A4BBDB1C0D800158A51865B7376@SSIEXCH-MB3.ssi.samsung.com</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>Hi Ray,<br><br>We are still discussing internally. We will let you know which option we vote for soon!<br><br>Regards,<br>Judy<br><br>From: <a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a> [<a href="mailto:nvmewin-bounces@lists.openfabrics.org">mailto:nvmewin-bounces@lists.openfabrics.org</a>] On Behalf Of Robles, Raymond C<br>Sent: Thursday, January 14, 2016 3:55 PM<br>To: 'nvmewin@lists.openfabrics.org'<br>Subject: [nvmewin] Happy New Year... and status update<br><br>Hello and Happy New Year,<br><br>I hope everyone had a great holiday season and is off to a great start to the new year!<br><br>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...<br><br><br>* Namespace Management (Intel)<br><br>* Perf Opts (Samsung)<br><br>* Win 8.1 Timers (Samsung)<br><br>* EOL Read Only (Samsung)<br><br>* Concurrent channels (Google)<br><br>The namespace management patch will be sent out for review tomorrow (look for the patch email from Carolyn)... stay tuned!!!<br><br>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.<br><br><br>1. Release what is in the trunk today (or after the namespace management patch)... and call that the 2015 release (albeit later than expected)<br><br>2. 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.<br><br>3. 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.<br><br>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.<br><br>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?<br><br>Thanks,<br>Ray<br><br>[<a href="cid:image001.png@01CB3870.4BB88E70">cid:image001.png@01CB3870.4BB88E70</a>]<br>Raymond C. Robles<br>Non-Volatile Memory Solutions Group<br>Intel Corporation<br>Office: 480-554-2600<br>Mobile: 480-399-0645<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/244aa8e7/attachment-0001.html">http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/244aa8e7/attachment-0001.html</a>><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image001.png<br>Type: image/png<br>Size: 1756 bytes<br>Desc: image001.png<br>URL: <<a href="http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/244aa8e7/attachment-0001.png">http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/244aa8e7/attachment-0001.png</a>><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 19 Jan 2016 14:41:36 +0000<br>From: Thomas Freeman <<a href="mailto:thomas.freeman@hgst.com">thomas.freeman@hgst.com</a>><br>To: "Robles, Raymond C" <<a href="mailto:raymond.c.robles@intel.com">raymond.c.robles@intel.com</a>><br>Cc: "'nvmewin@lists.openfabrics.org'" <<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>><br>Subject: Re: [nvmewin] Happy New Year... and status update<br>Message-ID:<br> <<a href="mailto:BLUPR04MB6734B5581755C45230DDB33E9C10@BLUPR04MB673.namprd04.prod.outlook.com">BLUPR04MB6734B5581755C45230DDB33E9C10@BLUPR04MB673.namprd04.prod.outlook.com</a>><br> <br>Content-Type: text/plain; charset="us-ascii"<br><br>Thanks for the response Ray.<br>I'm fine with option 3.<br><br>Tom Freeman<br>Software Engineer, Device Manager and Driver Development<br>HGST, a Western Digital company<br><a href="mailto:thomas.freeman@hgst.com%3cmailto:thomas.freeman@hgst.com">thomas.freeman@hgst.com<mailto:thomas.freeman@hgst.com</a>><br>507-322-2311<br><br>[HGST_Logo_email]<br>3605 Hwy 52 N<br>Rochester, MN 55901<br><a href="http://www.hgst.com%3chttps:/hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/">www.hgst.com<https://hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/</a>><br><br>From: Robles, Raymond C [<a href="mailto:raymond.c.robles@intel.com">mailto:raymond.c.robles@intel.com</a>]<br>Sent: Friday, January 15, 2016 3:54 PM<br>To: Thomas Freeman <<a href="mailto:thomas.freeman@hgst.com">thomas.freeman@hgst.com</a>><br>Cc: 'nvmewin@lists.openfabrics.org' <<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>><br>Subject: RE: Happy New Year... and status update<br><br>Hi Tom,<br><br>Great questions... here are my thoughts. But I encourage others to chime in as well.<br><br>Is this purely a question of how the changes are packaged? [RCR] Exactly! I am merely making a suggestion that will ease the burden of having mandatory releases... as well as having to adhere to a schedule that really has no meaning to any particular product since the OFA driver is a reference driver. Much like the Linux community, any vendor can take our baseline and package it up as needed, but for the community itself, it just manages bug fix and feature patches as they come in.<br><br>Or do any of these options imply what type of fixes/changes will be delivered in the future? i.e. Does choosing option 3 imply that the driver is going into purely maintenance mode? [RCR] Not at all. Option 3 is simply us doing what we've done all along... with the exception of not doing any "official releases". All bug fix and feature patches would still be graciously accepted... and welcome :).<br><br>Or with that option, would there still be a coordinated effort to release new function along with fixes? [RCR] Exactly... see above responses.<br><br>Does this answer your questions Tom?<br><br>Thanks,<br>Ray<br><br>From: Thomas Freeman [<a href="mailto:thomas.freeman@hgst.com">mailto:thomas.freeman@hgst.com</a>]<br>Sent: Friday, January 15, 2016 9:04 AM<br>To: Robles, Raymond C; 'nvmewin@lists.openfabrics.org'<br>Subject: RE: Happy New Year... and status update<br><br>Ray,<br>Is this purely a question of how the changes are packaged? Or do any of these options imply what type of fixes/changes will be delivered in the future? i.e. Does choosing option 3 imply that the driver is going into purely maintenance mode? Or with that option, would there still be a coordinated effort to release new function along with fixes?<br>Thanks,<br>Tom Freeman<br>Software Engineer, Device Manager and Driver Development<br>HGST, a Western Digital company<br><a href="mailto:thomas.freeman@hgst.com%3cmailto:thomas.freeman@hgst.com">thomas.freeman@hgst.com<mailto:thomas.freeman@hgst.com</a>><br>507-322-2311<br><br>[HGST_Logo_email]<br>3605 Hwy 52 N<br>Rochester, MN 55901<br><a href="http://www.hgst.com%3chttps:/hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/">www.hgst.com<https://hgst.jiveon.com/external-link.jspa?url=http://www.hgst.com/</a>><br><br>From: <a href="mailto:nvmewin-bounces@lists.openfabrics.org%3cmailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org<mailto:nvmewin-bounces@lists.openfabrics.org</a>> [<a href="mailto:nvmewin-bounces@lists.openfabrics.org">mailto:nvmewin-bounces@lists.openfabrics.org</a>] On Behalf Of Robles, Raymond C<br>Sent: Thursday, January 14, 2016 5:55 PM<br>To: 'nvmewin@lists.openfabrics.org' <<a href="mailto:nvmewin@lists.openfabrics.org%3cmailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org<mailto:nvmewin@lists.openfabrics.org</a>>><br>Subject: [nvmewin] Happy New Year... and status update<br><br>Hello and Happy New Year,<br><br>I hope everyone had a great holiday season and is off to a great start to the new year!<br><br>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...<br><br><br>* Namespace Management (Intel)<br><br>* Perf Opts (Samsung)<br><br>* Win 8.1 Timers (Samsung)<br><br>* EOL Read Only (Samsung)<br><br>* Concurrent channels (Google)<br><br>The namespace management patch will be sent out for review tomorrow (look for the patch email from Carolyn)... stay tuned!!!<br><br>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.<br><br><br>1. Release what is in the trunk today (or after the namespace management patch)... and call that the 2015 release (albeit later than expected)<br><br>2. 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.<br><br>3. 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.<br><br>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.<br><br>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?<br><br>Thanks,<br>Ray<br><br>[<a href="cid:image001.png@01CB3870.4BB88E70">cid:image001.png@01CB3870.4BB88E70</a>]<br>Raymond C. Robles<br>Non-Volatile Memory Solutions Group<br>Intel Corporation<br>Office: 480-554-2600<br>Mobile: 480-399-0645<br><br>HGST E-mail Confidentiality Notice & Disclaimer:<br>This e-mail and any files transmitted with it may contain confidential or legally privileged information of HGST and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.<br>HGST E-mail Confidentiality Notice & Disclaimer:<br>This e-mail and any files transmitted with it may contain confidential or legally privileged information of HGST and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/9f41dafe/attachment.html">http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/9f41dafe/attachment.html</a>><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image001.png<br>Type: image/png<br>Size: 4274 bytes<br>Desc: image001.png<br>URL: <<a href="http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/9f41dafe/attachment.png">http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/9f41dafe/attachment.png</a>><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image002.png<br>Type: image/png<br>Size: 1756 bytes<br>Desc: image002.png<br>URL: <<a href="http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/9f41dafe/attachment-0001.png">http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160119/9f41dafe/attachment-0001.png</a>><br><br>------------------------------<br><br>_______________________________________________<br>nvmewin mailing list<br><a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br><a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><br><br><br>End of nvmewin Digest, Vol 49, Issue 4<br>**************************************<br><br><p> </p><p> </p><o:p></o:p></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='border:solid windowtext 1.0pt;padding:0in'><img border=0 width=100 height=100 id="_x0000_i1026" src="cid:image002.jpg@01D15394.D39900A0" alt="Image removed by sender."></span><o:p></o:p></p><p class=MsoNormal><strong><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>HGST E-mail Confidentiality Notice & Disclaimer:</span></strong><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>This e-mail and any files transmitted with it may contain confidential or legally privileged information of HGST and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.<o:p></o:p></span></p></div></body></html>