<div dir="ltr">we are running this in a virtual machine, and we do see a perf difference with concurrent channels. We did not observe any performance drop with synchronized access to the list entry.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 10, 2016 at 7:15 AM, SUMAN PRAKASH B <span dir="ltr"><<a href="mailto:suman.p@samsung.com" target="_blank">suman.p@samsung.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri">Hi Iuliu,</span></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri"></span> </p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri">As you have the implementation in place, can you let us know if there is any performance improvement when STOR_PERF_CONCURRENT_CHANNELS is set in case of #core and #queues not matching.</span></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri">Also, if there is any drop in performance if the list entry and doorbell is protected after setting STOR_PERF_CONCURRENT_CHANNELS.</span></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri"></span> </p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri">Perhaps a bit off topic:</span></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri">Even in case when #cores and #queues are same and when STOR_PERF_CONCURRENT_CHANNELS is set, we did not observe any performance gain. Maybe we are hitting the max performance from device even without setting STOR_PERF_CONCURRENT_CHANNELS. Can you please let us know your observation?</span></p><span class="">
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri"></span> </p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri">Thanks,</span></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:Calibri">Suman</span></p>
<p> </p>
<p>------- <b>Original Message</b> -------</p>
<p><b>Sender</b> : Robles, Raymond C<<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>></p>
</span><p><b>Date</b> : Jun 10, 2016 08:30 (GMT+05:30)</p>
<p><b>Title</b> : RE: review comments for patch from Google</p><div><div class="h5">
<p> </p>
<u></u>
<div>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Hi Judy, <u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Thanks for the additional info. I agree with the assessment. My statement was directed at the general direction of the solution… and the fact that I think option 1 is not as robust as option 2.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Thank you…<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Ray<u></u><u></u></span></p>
<p class="MsoNormal"><a name="m_4928340539283924386__MailEndCompose"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"><u></u> <u></u></span></a></p>
<div>
<div style="BORDER-TOP:#e1e1e1 1pt solid;BORDER-RIGHT:medium none;BORDER-BOTTOM:medium none;PADDING-BOTTOM:0in;PADDING-TOP:3pt;PADDING-LEFT:0in;BORDER-LEFT:medium none;PADDING-RIGHT:0in">
<p class="MsoNormal"><b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">From:</span></b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif"> Judy Brock [mailto:<a href="mailto:judy.brock@samsung.com" target="_blank">judy.brock@samsung.com</a>] <br><b>Sent:</b> Thursday, June 09, 2016 5:14 PM<br><b>To:</b> Robles, Raymond C <<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>>; Iuliu Rus <<a href="mailto:iuliur@google.com" target="_blank">iuliur@google.com</a>>; <a href="mailto:suman.p@samsung.com" target="_blank">suman.p@samsung.com</a><br><b>Cc:</b> <a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a><br><b>Subject:</b> RE: review comments for patch from Google<u></u><u></u></span></p></div></div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d">Hi Ray et al,<u></u><u></u></span></p>
<p class="MsoNormal" style="MARGIN-LEFT:0.5in;TEXT-INDENT:0.5in"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">[Suman wrote] >> Protect the listentry and doorbell before access/update<u></u><u></u></span></p>
<p class="MsoNormal" style="MARGIN-LEFT:0.5in;TEXT-INDENT:0.5in"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif"> >>Do not set STOR_PERF_CONCURRENT_CHANNELS when number of cores and queues are not same.</span><u></u><u></u></p>
<p class="MsoNormal" style="MARGIN-LEFT:0.5in;TEXT-INDENT:0.5in"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal" style="MARGIN-LEFT:0.5in;TEXT-INDENT:0.5in"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Ray wrote] >>In the case Suman points out, concurrent channels should still be enabled even if the number of cores and queues do not match. This is especially true for large core count systems (>128 logical cpu cores) but devices may only support 32 queues or less</span><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d">I think Suman was saying, we have two options: <u></u><u></u></span></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><span>1.<span style="FONT-SIZE:7pt;FONT-FAMILY:"Times New Roman";FONT-VARIANT:normal;FONT-STYLE:normal;LINE-HEIGHT:normal"> </span></span></span><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d">either don’t enable it at all if # cores != #queues or <u></u><u></u></span></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><span>2.<span style="FONT-SIZE:7pt;FONT-FAMILY:"Times New Roman";FONT-VARIANT:normal;FONT-STYLE:normal;LINE-HEIGHT:normal"> </span></span></span><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d">protect both the list entries and doorbell writes before any accesses/updates if #cores != #queues. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d">So we will need to check to see if we need to use locks or not in the performance path based on whether #cores and # queues DO match or not if we want to enable concurrent channels no matter what. It’s probably better than option 1) above if this is a configuration that can come up frequently.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d">Judy<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;BORDER-BOTTOM:medium none;PADDING-BOTTOM:0in;PADDING-TOP:3pt;PADDING-LEFT:0in;BORDER-LEFT:medium none;PADDING-RIGHT:0in">
<p class="MsoNormal"><b><span style="FONT-SIZE:10pt;FONT-FAMILY:"Tahoma",sans-serif">From:</span></b><span style="FONT-SIZE:10pt;FONT-FAMILY:"Tahoma",sans-serif"> nvmewin [<a href="mailto:nvmewin-bounces@lists.openfabrics.org" target="_blank">mailto:nvmewin-bounces@lists.openfabrics.org</a>] <b>On Behalf Of </b>Robles, Raymond C<br><b>Sent:</b> Thursday, June 09, 2016 2:32 PM<br><b>To:</b> Iuliu Rus; <a href="mailto:suman.p@samsung.com" target="_blank">suman.p@samsung.com</a><br><b>Cc:</b> <a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a><br><b>Subject:</b> Re: [nvmewin] review comments for patch from Google<u></u><u></u></span></p></div></div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Hi Iuliu/Suman,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">I’m of the opinion that any solution provided should be as robust as possible. In the case Suman points out, concurrent channels should still be enabled even if the number of cores and queues do not match. This is especially true for large core count systems (>128 logical cpu cores) but devices may only support 32 queues or less. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Thank you…<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Ray<u></u><u></u></span></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">From:</span></b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif"> Iuliu Rus <a href="mailto:[mailto:iuliur@google.com]" target="_blank">[mailto:iuliur@google.com]</a> <br><b>Sent:</b> Thursday, June 09, 2016 2:09 PM<br><b>To:</b> <a href="mailto:suman.p@samsung.com" target="_blank">suman.p@samsung.com</a><br><b>Cc:</b> Robles, Raymond C <<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>>; <a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a><br><b>Subject:</b> Re: review comments for patch from Google<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Which one do you prefer? Our google driver has the synchronization in place already for a different reason. Or, I can follow your second suggestion.<u></u><u></u></p></div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Thu, Jun 9, 2016 at 7:39 AM, SUMAN PRAKASH B <<a href="mailto:suman.p@samsung.com" target="_blank">suman.p@samsung.com</a>> wrote:<u></u><u></u></p>
<blockquote style="BORDER-TOP:medium none;BORDER-RIGHT:medium none;BORDER-BOTTOM:medium none;PADDING-BOTTOM:0in;PADDING-TOP:0in;PADDING-LEFT:6pt;MARGIN:5pt 0in 5pt 4.8pt;BORDER-LEFT:#cccccc 1pt solid;PADDING-RIGHT:0in">
<div>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">Hi Iuliu,</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">Please find my review comments below:</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">1. If the number of Cores and Queues supported by device are not same, then setting STOR_PERF_CONCURRENT_CHANNELS will corrupt the submission queue. For example, if device has 4 queues and connected to target PC which has 8 logical processors, and if STOR_PERF_CONCURRENT_CHANNELS is set, all the 8 logical processors will get startIo calls concurrently. As per OFA driver NUMA design, the IO Queue 1 will be shared by core 0 and core 4. There is possibility that core 0 and core 4 will get startio() calls concurrently and will access/update the listenty and queue 1 doorbell register at same time, which will lead to listentry and doorbell register corruption. <br>This problem can be address by following ways:<br>a. Protect the listentry and doorbell before access/update.<br>b. Do not set STOR_PERF_CONCURRENT_CHANNELS when number of cores and queues are not same.</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">2. We can use pRMT->NumActiveCores which is updated in NVMeEnumNumaCores() instead of using KeQueryActiveProcessorCountEx/KeQueryActiveProcessorCount.</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">Please let us know your opinion.</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">Thanks,<br>Suman</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p>------- <b>Original Message</b> -------<u></u><u></u></p>
<p><b>Sender</b> : Robles, Raymond C<<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>><u></u><u></u></p>
<p><b>Date</b> : Jun 09, 2016 03:56 (GMT+05:30)<u></u><u></u></p>
<p><b>Title</b> : Re: [nvmewin] Happy New Year... and status update<u></u><u></u></p>
<p> <u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Thank you Iuliu!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;BACKGROUND:yellow;COLOR:#002060">Reviewing companies, please try to target the review completion for 2 weeks from today (6/22/16).</span><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Thank you!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">From:</span></b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif"> Iuliu Rus [mailto:<a href="mailto:iuliur@google.com" target="_blank">iuliur@google.com</a>] <br><b>Sent:</b> Wednesday, June 08, 2016 12:26 PM<br><b>To:</b> Robles, Raymond C <<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>><br><b>Cc:</b> <a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a><br><b>Subject:</b> Re: Happy New Year... and status update</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">I attached our patch. <u></u><u></u></p></div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">On Tue, Jun 7, 2016 at 2:37 PM, Iuliu Rus <<a href="mailto:iuliur@google.com" target="_blank">iuliur@google.com</a>> wrote:<u></u><u></u></p>
<blockquote style="BORDER-TOP:medium none;BORDER-RIGHT:medium none;BORDER-BOTTOM:medium none;PADDING-BOTTOM:0in;PADDING-TOP:0in;PADDING-LEFT:6pt;MARGIN:5pt 0in 5pt 4.8pt;BORDER-LEFT:#cccccc 1pt solid;PADDING-RIGHT:0in">
<div>
<p class="MsoNormal">Let me see if i can get it done by tomorrow eod...<u></u><u></u></p></div>
<div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">On Tue, Jun 7, 2016 at 2:31 PM, Robles, Raymond C <<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>> wrote:<u></u><u></u></p>
<blockquote style="BORDER-TOP:medium none;BORDER-RIGHT:medium none;BORDER-BOTTOM:medium none;PADDING-BOTTOM:0in;PADDING-TOP:0in;PADDING-LEFT:6pt;MARGIN:5pt 0in 5pt 4.8pt;BORDER-LEFT:#cccccc 1pt solid;PADDING-RIGHT:0in">
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Hi Iuliu,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">That’s great… thank you. Yes, the process is still the same (using SVN patches).</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Please let me know if you have any questions/comments. My only question for you is an ETA for the patch to be submitted.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Thank you…</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif;COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif">From:</span></b><span style="FONT-SIZE:11pt;FONT-FAMILY:"Calibri",sans-serif"> Iuliu Rus [mailto:<a href="mailto:iuliur@google.com" target="_blank">iuliur@google.com</a>] <br><b>Sent:</b> Tuesday, June 07, 2016 2:28 PM<br><b>To:</b> Robles, Raymond C <<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>><br><b>Cc:</b> <a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a><br><b>Subject:</b> Re: Happy New Year... and status update</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">Yes we can send that to you. Is the process still the same?<u></u><u></u></p></div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">On Tue, Jun 7, 2016 at 1:25 PM, Robles, Raymond C <<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>> wrote:<u></u><u></u></p>
<blockquote style="BORDER-TOP:medium none;BORDER-RIGHT:medium none;BORDER-BOTTOM:medium none;PADDING-BOTTOM:0in;PADDING-TOP:0in;PADDING-LEFT:6pt;MARGIN:5pt 0in 5pt 4.8pt;BORDER-LEFT:#cccccc 1pt solid;PADDING-RIGHT:0in">
<div>
<div>
<p class="MsoNormal"><span style="COLOR:#002060">Hello Iuliu,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="COLOR:#002060">As the OFA community is closing on its mid-year release, we have only one more patch that was targeted… concurrent channels. Will Google still be submitting the concurrent channels patch?</span><u></u><u></u></p>
<p class="MsoNormal"><span style="COLOR:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="COLOR:#002060">Thank you…</span><u></u><u></u></p>
<p class="MsoNormal"><span style="COLOR:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="COLOR:#002060"> </span><u></u><u></u></p>
<div>
<div style="BORDER-TOP:#e1e1e1 1pt solid;BORDER-RIGHT:medium none;BORDER-BOTTOM:medium none;PADDING-BOTTOM:0in;PADDING-TOP:3pt;PADDING-LEFT:0in;BORDER-LEFT:medium none;PADDING-RIGHT:0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:nvmewin-bounces@lists.openfabrics.org" target="_blank">nvmewin-bounces@lists.openfabrics.org</a> [mailto:<a href="mailto:nvmewin-bounces@lists.openfabrics.org" target="_blank">nvmewin-bounces@lists.openfabrics.org</a>] <b>On Behalf Of </b>Robles, Raymond C<br><b>Sent:</b> Thursday, January 14, 2016 4:55 PM<br><b>To:</b> '<a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a>' <<a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a>><br><b>Subject:</b> [nvmewin] Happy New Year... and status update<u></u><u></u></p></div></div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">Hello and Happy New Year,</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">I hope everyone had a great holiday season and is off to a great start to the new year!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;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…</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:Symbol;COLOR:#44546a">·</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">Namespace Management (Intel)</span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:Symbol;COLOR:#44546a">·</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">Perf Opts (Samsung) </span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:Symbol;COLOR:#44546a">·</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">Win 8.1 Timers (Samsung)</span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:Symbol;COLOR:#44546a">·</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">EOL Read Only (Samsung)</span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:Symbol;COLOR:#44546a">·</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">Concurrent channels (Google)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">The namespace management patch will be sent out for review tomorrow (look for the patch email from Carolyn)… stay tuned!!!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;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. </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">1.</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;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)</span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">2.</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;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.</span><u></u><u></u></p>
<p><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">3.</span><span style="FONT-SIZE:7pt;COLOR:#44546a"> </span><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;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.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;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.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;BACKGROUND:yellow;COLOR:#44546a">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><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">Thanks,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#1f497d"><img border="0" alt="cid:image001.png@01CB3870.4BB88E70" src="cid:DPBBX1FI5HHV@namo.co.kr" width="54" height="39"></span></b><u></u><u></u></p>
<p class="MsoNormal"><b><i><span style="FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#1f497d">Raymond C. Robles</span></i></b><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#1f497d">Non-Volatile Memory Solutions Group</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#1f497d">Intel Corporation</span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#1f497d">Office: <a href="tel:480-554-2600" target="_blank">480-554-2600</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="FONT-SIZE:10pt;FONT-FAMILY:"Intel Clear",sans-serif;COLOR:#1f497d">Mobile: <a href="tel:480-399-0645" target="_blank">480-399-0645</a></span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p></div></div></div></div></blockquote></div>
<p class="MsoNormal"> <u></u><u></u></p></div></div></div></div></div></blockquote></div>
<p class="MsoNormal"> <u></u><u></u></p></div></div></div></blockquote></div>
<p class="MsoNormal"> <u></u><u></u></p></div></div>
<p> <u></u><u></u></p>
<p> <u></u><u></u></p>
<table cellpadding="0" border="0">
<tbody>
<tr>
<td style="PADDING-BOTTOM:0.75pt;PADDING-TOP:0.75pt;PADDING-LEFT:0.75pt;PADDING-RIGHT:0.75pt">
<p><img border="0" src="cid:ESYT2XYNX48N@namo.co.kr" width="520" height="144"><u></u><u></u></p></td></tr></tbody></table></div>
<p class="MsoNormal"><img border="0" src="http://ext.samsung.net/mailcheck/SeenTimeChecker?do=9226f2572c3ad117df6a46883b3f3dde1d283838fa336dda194352576c69fe9bfdd53f331c9856e34bea3c1765014a1208cece8541bc14eacf878f9a26ce15a0"><u></u><u></u></p></blockquote></div>
<p class="MsoNormal"><u></u> <u></u></p></div></div><u></u>
<p> </p>
<p> </p>
</div></div><table>
<tbody>
<tr>
<td>
<p><img border="0" src="cid:MKNRCZHWKC3T@namo.co.kr"></p></td></tr></tbody></table></div><img src="http://ext.samsung.net/mailcheck/SeenTimeChecker?do=36e611fbbc499bdb45df2c678ea6c804daf257cfe78672b8194352576c69fe9bfdd53f331c9856e34bea3c1765014a1208cece8541bc14eacf878f9a26ce15a0" border="0" width="0" height="0"></blockquote></div><br></div>