<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Verdana","sans-serif";
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="color:#1f497d">Amber/Uma,</span></p><p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Sorry for the delayed response, I’m trying to get caught back up after vacation.</span></p><p class="MsoNormal"><span style="color:#1f497d"> </span></p><p class="MsoNormal">
<span style="color:#1f497d">First I should say that I am in no way leading the SCSI to NVMe translation effort. I’m just the last person to contribute. The spec has been a community effort with many companies contributing.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p><p class="MsoNormal"><span style="color:#1f497d">I didn’t contribute or modify the text you reference, but I’ll give you my interpretation of it.</span></p><p class="MsoNormal">
<span style="color:#1f497d"> </span></p><p class="MsoNormal"><span style="color:#1f497d">There are many commands that can be roughly translated between SCSI and NVMe. However, there are also some SCSI commands that have no direct translation to an NVMe command. In the case where there isn’t a direct translation, the driver implementing the SCSI to NVMe translation layer must respond to the SCSI commands in a way that will make a SCSI driver sending these commands happy. I guess you can say that the driver has to emulate these commands that can’t be translated. The translation spec does indicate how you are supposed to respond to commands like Request Sense, but the spec is certainly pretty light on detail. The SCSI to NVMe translation spec serves the same purpose as the T10 SAT (SCSI to ATA translation) spec, but the NVMe spec is much less mature. If you’re interested, I think the NVMe community would welcome any proposals you have to help update the NVMe translations to the same level as the ATA translations.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p><p class="MsoNormal"><span style="color:#1f497d">Thanks,</span></p><p class="MsoNormal"><span style="color:#1f497d">Guy</span></p><p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Huffman, Amber [mailto:<a href="mailto:amber.huffman@intel.com">amber.huffman@intel.com</a>] <br>
<b>Sent:</b> Wednesday, August 06, 2014 1:19 PM<br><b>To:</b> Uma Parepalli; <a href="mailto:technical@nvmexpress.org">technical@nvmexpress.org</a>; <a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>; <a href="mailto:info@nvmexpress.org">info@nvmexpress.org</a><br>
<b>Cc:</b> Guy Kendall (<a href="mailto:guy.kendall@avagotech.com">guy.kendall@avagotech.com</a>)<br><b>Subject:</b> RE: SCSI to NVMe Mapping</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Hi Uma,</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Guy, cc:ed, has been leading our efforts on SCSI to NVMe translation. I’d suggest that you get together with Guy for 15 minutes to discuss and determine whether anything needs to be added to the list of translation enhancements in this area. I expect we’ll start looking at some enhancements to the translation document in September, after revision 1.2 is done.</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Thanks,</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">Amber </span></p><p class="MsoNormal"><a name="_MailEndCompose"></a><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d"> </span></p>
<div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b>From:</b> <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>] <b>On Behalf Of </b>Uma Parepalli<br>
<b>Sent:</b> Tuesday, August 5, 2014 6:40 PM<br><b>To:</b> <a href="mailto:technical@nvmexpress.org">technical@nvmexpress.org</a>; <a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>; <a href="mailto:info@nvmexpress.org">info@nvmexpress.org</a><br>
<b>Subject:</b> [nvmewin] SCSI to NVMe Mapping</p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size:14.0pt">Hi Amber/Peter/Kevin/Kwok and all, </span></p><p class="MsoNormal"><span style="font-size:14.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">The “<span style="color:black">NVM Express: SCSI Translation Reference” document doesn’t provide a direct mapping for “REQUEST SENSE” but has the following Note:</span></span></p>
<p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif"">“MODE SELECT(6), MODE SELECT(10), REQUEST SENSE and TEST UNIT READY commands do not map 1-to-1 to NVM Express commands; a device driver should translate as specified in the referenced sections.”</span></p>
<p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif""> </span></p><p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif"">Could you please explain what would be the above commands are equal to in the NVMe world?</span></p>
<p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif"">I would like to hear from both NVMe forum and Windows Driver world.</span></p><p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif"">Attaching the document since I know you (we) are all busy with Flash Memory Summit </span><span style="font-size:14.0pt;font-family:Wingdings">J</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif""></span></p>
<p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif""> </span></p><p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif"">Thank you,</span></p>
<p class="Default"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif"">Uma</span></p><p class="MsoNormal"><span style="font-size:14.0pt">Uma Parepalli</span></p><p class="MsoNormal"><span style="font-size:14.0pt">Cell: 408 805 9260</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><a href="mailto:uma.parepalli@skhms.com">uma.parepalli@skhms.com</a></span></p><p class="MsoNormal"><span style="font-size:14.0pt">SK Hynix Memory Solutions Inc.</span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">3103 North 1<sup>st</sup> Street, San Jose, CA</span></p><p class="MsoNormal"><span style="font-size:14.0pt"> </span></p><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">The information contained in this e-mail is considered confidential of SK hynix memory solutions Inc. and intended only for the persons addressed or copied in this e-mail. Any unauthorized use, dissemination of the information, or copying of this message is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email. </span></p>
</div></body></html>