<div dir="ltr">Let me know if i have to sync to the latest and re-do the patch.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 16, 2016 at 2:10 PM, Iuliu Rus <span dir="ltr"><<a href="mailto:iuliur@google.com" target="_blank">iuliur@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">We already have a pool of locks - the dpc locks, which is what i'm using in my latest patch. You cannot create spinlocks directly in a storport driver, the only option is to use either the StartIoLock, the dpc lock, the interrupt lock or one of the MSI locks.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 16, 2016 at 2:04 PM, Robles, Raymond C <span dir="ltr"><<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Hello,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Here are my thoughts…
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">In short, I agree with Thomas’s assessment.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Concurrent channels allows Storport to call StartIo concurrently… and with no locks. Therefore the locking of critical sections is now the responsibility of the
miniport.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Any solution proposed should protect critical resources (cmd id pool, cmd entries, doorbells) with a lock that is granular enough for our driver, but not at the
visibility of the OS or Storport. Acquiring the StartIo lock to protect resources in our driver only is too broad of a lock. My suggestion would be to create a pool of locks (one for every SQ/CQ pair) that is maintained within our driver. Again, crashdump
mode is a non-issue because it is single threaded.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Thank you…<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Ray<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><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"> Thomas Freeman [mailto:<a href="mailto:thomas.freeman@hgst.com" target="_blank">thomas.freeman@hgst.com</a>]
<br>
<b>Sent:</b> Thursday, June 16, 2016 1:51 PM<br>
<b>To:</b> Iuliu Rus <<a href="mailto:iuliur@google.com" target="_blank">iuliur@google.com</a>><span><br>
<b>Cc:</b> Robles, Raymond C <<a href="mailto:raymond.c.robles@intel.com" target="_blank">raymond.c.robles@intel.com</a>>; nvmewin <<a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a>><br>
</span><b>Subject:</b> RE: [nvmewin] review comments for patch from Google<u></u><u></u></span></p>
</div>
</div><div><div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi Iuliu,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Here my view, I hope someone else can chime in to verify or correct what I'm saying<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The purpose of the concurrent channels change is to prevent Storport from acquiring the StartIo lock before calling Startio. This allows multiple simultaneous
calls to StartIo. If you require ProcessIo get the StartIo lock, you are replicating what Storport used to - it defeats the point of concurrent channels.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Here is my suggestion for what needs to be changed<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">1. There is no need for StartIo Locks - remove the requests to acquire them<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">2. Acquire the Dpc locks in the following situations<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> -ProcessIo, before calling GetCmdEntry - if there is queue sharing<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> -ProcessIo, before calling IssueCmd - always<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> -IoCompletionRoutine, before calling NVMeCompleteCmd - if there is queue sharing<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> -recoveryDpcRoutine - get all of the Dpc locks<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Here is my reasoning<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-GetCmdEntry and NVMeCompleteCmd both access the FreeQList. With queue sharing, these could run simultaneously and have a collision when they update the list.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-IssueCmd. With queue sharing, different cpu's could attempt to put entries on the queue simultaneously. But, to make RecoveryDpcRoutine work, this must be protected
by the dpcLock whether or not there is queue sharing. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I think this will address the deadlock problem I reported also.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Tom Freeman<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Software Engineer, Device Manager and Driver Development<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Western Digital Corporation<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">e.
<a href="mailto:Thomas.freeman@hgst.com" target="_blank">Thomas.freeman@hgst.com</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">o. <a href="tel:%2B1-507-322-2311" value="+15073222311" target="_blank">+1-507-322-2311</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><img border="0" width="150" height="47" src="cid:image001.jpg@01D1C7D7.FE08CA20"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><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"> Iuliu Rus [<a href="mailto:iuliur@google.com" target="_blank">mailto:iuliur@google.com</a>]
<br>
<b>Sent:</b> Thursday, June 16, 2016 2:42 PM<br>
<b>To:</b> Thomas Freeman <<a href="mailto:thomas.freeman@hgst.com" target="_blank">thomas.freeman@hgst.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>>; nvmewin <<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>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Here's my revised patch for concurrent channels. The synchronization rules are now as follows:<u></u><u></u></p>
<div>
<p class="MsoNormal">1. Init is single threaded so it doesn't matter if acquirelock is true or false<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">2. Anything called from the DPC has to call ProcessIo with false, since the dpc spinlock is already acquired.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">3. Anything called from StartIo has to call ProcessIo with true, since now the startio is not automatically acquired.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thomas, i think the bug that you found is because the ProcessIo was incorrectly called with TRUE instead of FALSE.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Let me know what are your thoughts on this.<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Thu, Jun 16, 2016 at 10:41 AM, Iuliu Rus <<a href="mailto:iuliur@google.com" target="_blank">iuliur@google.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Guys, am i OK continuing with the patch on the current code base or do you want me to wait until you pull in some more changes?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Jun 15, 2016 at 8:37 AM, Thomas Freeman <<a href="mailto:thomas.freeman@hgst.com" target="_blank">thomas.freeman@hgst.com</a>> wrote:<u></u><u></u></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Ray,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">It appears that the latest patch file from Iuliu is applied to revision 137. I don’t see Suman’s changes
in that revision.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">As an example, the use of StorPortRequestTimer is not in nvmeStat.c.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I thought there were some newer revisions than 137, but 137 is the latest I’m able to download.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">137 is also the revision that appears when I go to
<a href="https://svn.openfabrics.org/svnrepo/nvmewin/" target="_blank">https://svn.openfabrics.org/svnrepo/nvmewin/</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">SVN is giving me some troubles, so I can’t tell for sure if this is my environment or a server issue.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Tom Freeman</span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Software Engineer, Device Manager and Driver Development</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">Western Digital Corporation</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">e.
<a href="mailto:Thomas.freeman@hgst.com" target="_blank">Thomas.freeman@hgst.com</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#1f497d">o.
<a href="tel:%2B1-507-322-2311" target="_blank">+1-507-322-2311</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><img border="0" width="150" height="47" src="cid:image003.jpg@01D1C7D7.FE08CA20"></span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><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"> nvmewin [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> Friday, June 10, 2016 12:23 PM<br>
<b>To:</b> 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> nvmewin <<a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a>></span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><br>
<b>Subject:</b> Re: [nvmewin] review comments for patch from Google<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Hi Iuliu,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">If you send out the updated patch with the protection in place for both list entries and doorbells,
I can run it on an Intel NVMe SSD (P3700) and see if there is any performance impact (up or down).</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Thank you…</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><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"> Iuliu Rus [</span><a href="mailto:iuliur@google.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">mailto:iuliur@google.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">]
<br>
<b>Sent:</b> Friday, June 10, 2016 10:17 AM<br>
<b>To:</b> </span><a href="mailto:suman.p@samsung.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">suman.p@samsung.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Cc:</b> Robles, Raymond C <</span><a href="mailto:raymond.c.robles@intel.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">raymond.c.robles@intel.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;
Judy Brock <</span><a href="mailto:judy.brock@samsung.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">judy.brock@samsung.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>; nvmewin <</span><a href="mailto:nvmewin@lists.openfabrics.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">nvmewin@lists.openfabrics.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Subject:</b> Re: RE: review comments for patch from Google</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">On Fri, Jun 10, 2016 at 7:15 AM, SUMAN PRAKASH B <<a href="mailto:suman.p@samsung.com" target="_blank">suman.p@samsung.com</a>> wrote:<u></u><u></u></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Iuliu,</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">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><u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Also, if there is any drop in performance if the list entry and doorbell is protected after setting STOR_PERF_CONCURRENT_CHANNELS.</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Perhaps a bit off topic:</span><u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">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><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks,</span><u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">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 10, 2016 08:30 (GMT+05:30)<u></u><u></u></p>
<p><b>Title</b> : RE: review comments for patch from Google<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p> <u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Hi Judy,
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Thank you…</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><a name="m_-7296186319888222386_m_971401771860741271_m_-6943154206965196345_m_-65521341744167"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span></a><u></u><u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><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"> Judy Brock [mailto:</span><a href="mailto:judy.brock@samsung.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">judy.brock@samsung.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">]
<br>
<b>Sent:</b> Thursday, June 09, 2016 5:14 PM<br>
<b>To:</b> Robles, Raymond C <</span><a href="mailto:raymond.c.robles@intel.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">raymond.c.robles@intel.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;
Iuliu Rus <</span><a href="mailto:iuliur@google.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">iuliur@google.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;
</span><a href="mailto:suman.p@samsung.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">suman.p@samsung.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Cc:</b> </span><a href="mailto:nvmewin@lists.openfabrics.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">nvmewin@lists.openfabrics.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Subject:</b> RE: review comments for patch from Google</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi Ray et al,</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:.5in">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[Suman wrote] >> Protect the listentry and doorbell before access/update</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:.5in">
<span style="font-size:11.0pt;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:.5in;text-indent:.5in">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:.5in">
<span style="font-size:11.0pt;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><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I think Suman was saying, we have two options:
</span><u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">1.</span><span style="font-size:7.0pt;color:#1f497d">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">either don’t enable it at all if # cores != #queues or
</span><u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">2.</span><span style="font-size:7.0pt;color:#1f497d">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">protect both the list entries and doorbell writes before any accesses/updates if #cores != #queues.
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Thanks,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Judy</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></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"> nvmewin [</span><a href="mailto:nvmewin-bounces@lists.openfabrics.org" target="_blank"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:nvmewin-bounces@lists.openfabrics.org</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<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; </span><a href="mailto:suman.p@samsung.com" target="_blank"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">suman.p@samsung.com</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"><br>
<b>Cc:</b> </span><a href="mailto:nvmewin@lists.openfabrics.org" target="_blank"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">nvmewin@lists.openfabrics.org</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"><br>
<b>Subject:</b> Re: [nvmewin] review comments for patch from Google</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Hi Iuliu/Suman,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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.
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Thank you…</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><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"> Iuliu Rus
</span><a href="mailto:[mailto:iuliur@google.com]" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">[mailto:iuliur@google.com]</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">
<br>
<b>Sent:</b> Thursday, June 09, 2016 2:09 PM<br>
<b>To:</b> </span><a href="mailto:suman.p@samsung.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">suman.p@samsung.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Cc:</b> Robles, Raymond C <</span><a href="mailto:raymond.c.robles@intel.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">raymond.c.robles@intel.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;
</span><a href="mailto:nvmewin@lists.openfabrics.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">nvmewin@lists.openfabrics.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Subject:</b> Re: review comments for patch from Google</span><u></u><u></u></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>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<div>
<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>
</div>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<p><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Iuliu,</span><u></u><u></u></p>
<p> <u></u><u></u></p>
<p><span style="font-size:11.0pt;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:11.0pt;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:11.0pt;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:11.0pt;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:11.0pt;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:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Thank you Iuliu!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060;background:yellow">Reviewing companies, please try to target the review completion for 2 weeks from
today (6/22/16).</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Thank you!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><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"> Iuliu Rus [mailto:</span><a href="mailto:iuliur@google.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">iuliur@google.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">]
<br>
<b>Sent:</b> Wednesday, June 08, 2016 12:26 PM<br>
<b>To:</b> Robles, Raymond C <</span><a href="mailto:raymond.c.robles@intel.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">raymond.c.robles@intel.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Cc:</b> </span><a href="mailto:nvmewin@lists.openfabrics.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">nvmewin@lists.openfabrics.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><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:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<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:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Hi Iuliu,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Thank you…</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#002060"> </span><u></u><u></u></p>
<p class="MsoNormal"><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"> Iuliu Rus [mailto:</span><a href="mailto:iuliur@google.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">iuliur@google.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">]
<br>
<b>Sent:</b> Tuesday, June 07, 2016 2:28 PM<br>
<b>To:</b> Robles, Raymond C <</span><a href="mailto:raymond.c.robles@intel.com" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">raymond.c.robles@intel.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Cc:</b> </span><a href="mailto:nvmewin@lists.openfabrics.org" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">nvmewin@lists.openfabrics.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><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:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<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:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 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:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p><span style="font-size:10.0pt;font-family:Symbol;color:#44546a">·</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">Namespace Management (Intel)</span><u></u><u></u></p>
<p><span style="font-size:10.0pt;font-family:Symbol;color:#44546a">·</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">Perf Opts (Samsung)
</span><u></u><u></u></p>
<p><span style="font-size:10.0pt;font-family:Symbol;color:#44546a">·</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">Win 8.1 Timers (Samsung)</span><u></u><u></u></p>
<p><span style="font-size:10.0pt;font-family:Symbol;color:#44546a">·</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">EOL Read Only (Samsung)</span><u></u><u></u></p>
<p><span style="font-size:10.0pt;font-family:Symbol;color:#44546a">·</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">Concurrent channels (Google)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">1.</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">2.</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">3.</span><span style="font-size:7.0pt;color:#44546a">
</span><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a;background: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><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">Thanks,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a">Ray</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#44546a"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#1f497d"><img border="0" width="54" height="39" src="cid:image004.png@01D1C7D7.FE08CA20" alt="cid:image001.png@01CB3870.4BB88E70"></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:10.0pt;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:10.0pt;font-family:"Intel Clear",sans-serif;color:#1f497d">Intel Corporation</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#1f497d">Office:
</span><a href="tel:480-554-2600" target="_blank"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif">480-554-2600</span></a><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif;color:#1f497d">Mobile:
</span><a href="tel:480-399-0645" target="_blank"><span style="font-size:10.0pt;font-family:"Intel Clear",sans-serif">480-399-0645</span></a><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>
</div>
</div>
<table border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><img border="0" width="520" height="144" src="cid:image005.gif@01D1C7D7.FE08CA20" alt="cid:image006.gif@01D1C6EF.5D9CDE20"><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="border:solid windowtext 1.0pt;padding:0in"><img border="0" width="32" height="32" src="cid:image006.jpg@01D1C7D7.FE08CA20" alt="Image removed by sender. http://ext.samsung.net/mailcheck/SeenTimeChecker?do=9226f2572c3ad117df6a46883b3f3dde1d283838fa336dda194352576c69fe9bfdd53f331c9856e34bea3c1765014a1208cece8541bc14eacf878f9a26ce15a0"></span><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p> <u></u><u></u></p>
<p> <u></u><u></u></p>
</div>
</div>
<table border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><img border="0" width="520" height="144" src="cid:image005.gif@01D1C7D7.FE08CA20" alt="cid:image006.gif@01D1C6EF.5D9CDE20"><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="border:solid windowtext 1.0pt;padding:0in"><img border="0" width="32" height="32" src="cid:image006.jpg@01D1C7D7.FE08CA20" alt="Image removed by sender. http://ext.samsung.net/mailcheck/SeenTimeChecker?do=36e611fbbc499bdb45df2c678ea6c804daf257cfe78672b8194352576c69fe9bfdd53f331c9856e34bea3c1765014a1208cece8541bc14eacf878f9a26ce15a0"></span><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal">Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:<u></u><u></u></p>
<div>
<p class="MsoNormal">This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, 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.<u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">_______________________________________________<br>
nvmewin mailing list<br>
<a href="mailto:nvmewin@lists.openfabrics.org" target="_blank">nvmewin@lists.openfabrics.org</a><br>
<a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin" target="_blank">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:<u></u><u></u></p>
<div>
<p class="MsoNormal">This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, 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.<u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>