<HTML xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:x = "urn:schemas-microsoft-com:office:excel" xmlns:dt = "uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE id=mysingle_style type=text/css>P {
MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt; FONT-FAMILY: Arial, arial; MARGIN-TOP: 5px
}
TD {
MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt; FONT-FAMILY: Arial, arial; MARGIN-TOP: 5px
}
LI {
MARGIN-BOTTOM: 5px; FONT-SIZE: 9pt; FONT-FAMILY: Arial, arial; MARGIN-TOP: 5px
}
BODY {
FONT-SIZE: 9pt; FONT-FAMILY: Arial, arial; MARGIN: 10px; LINE-HEIGHT: 1.4
}
</STYLE>
<META content=IE=5 http-equiv=X-UA-Compatible>
<META content=IE=5 http-equiv=X-UA-Compatible>
<META name=GENERATOR content="MSHTML 11.00.9600.18212"></HEAD>
<BODY>
<P><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri">Hi Carolyn,</SPAN></P>
<P><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri">We have reviewed the code and the changes look good, apart from the following minor comment:</SPAN></P>
<P><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri">1) File: nvmeStd.c, </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; mso-fareast-language: EN-US; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">Function: </SPAN><FONT size=2 face=Consolas><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; mso-fareast-language: EN-US; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">NVMeIoctlNamespaceMgmt</SPAN></FONT><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; mso-fareast-language: EN-US; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">(), Line no: 3978</SPAN></P>
<P><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri">memset is not required </SPAN><FONT size=2 face=Consolas><FONT size=2 face=Consolas><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri">as </SPAN><FONT size=2 face=Consolas><FONT style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri" size=2 face=Consolas>NVMeAllocatePool() will allocate memory for buffer and memset that buffer to zero.</FONT></FONT></FONT></FONT></P>
<P><FONT style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri" size=2 face=Consolas>Same is applicable for pRMT->pProcGroupTbl in NVMeEnumNumaCores() in nvmeInit.c, line no:370, <U>which is not part of Intel's patch</U>.</FONT></P>
<P><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri"></SPAN> </P>
<P><FONT style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri" size=2 face=Consolas>Anyway, we feel, if there is no other review comments from others, no need for Intel to submit updated patch after correcting the above. Samsung can make these changes when we submit our next patch after Intel's NS mgmt patch.</FONT></P>
<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> : Foster, Carolyn D<carolyn.d.foster@intel.com></P>
<P><B>Date</B> : Feb 26, 2016 21:57 (GMT+05:30)</P>
<P><B>Title</B> : Re: [nvmewin] Patch with changes for Namespace Management</P>
<P> </P>
<META name=Generator content=ActiveSquare>
<STYLE>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Consolas;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
LI.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
DIV.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
A:link {
TEXT-DECORATION: underline; COLOR: #0563c1; mso-style-priority: 99
}
SPAN.MsoHyperlink {
TEXT-DECORATION: underline; COLOR: #0563c1; mso-style-priority: 99
}
A:visited {
TEXT-DECORATION: underline; COLOR: #954f72; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
TEXT-DECORATION: underline; COLOR: #954f72; mso-style-priority: 99
}
P {
FONT-SIZE: 9pt; FONT-FAMILY: "Arial",sans-serif; MARGIN: 3.75pt 0in; mso-style-priority: 99
}
P.MsoListParagraph {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt 0.5in; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt 0.5in; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt 0.5in; mso-style-priority: 34
}
SPAN.EmailStyle19 {
FONT-FAMILY: "Calibri",sans-serif; COLOR: windowtext; mso-style-type: personal
}
SPAN.EmailStyle20 {
FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</STYLE>
<META content=IE=5 http-equiv=X-UA-Compatible><X-BODY lang=EN-US link="#0563C1" vlink="#954F72">
<DIV class=WordSection1>
<P class=MsoNormal>Hi all, <o:p></o:p></P>
<P class=MsoNormal>I am sending the updated patch incorporating feedback I received. The changes are listed below, along with my comments about the feedback I did not address. The password is intelnvme<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Patch updates:<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>Server 2012 was failing to shut down because of mismatched calls to StorportDeviceBusy and StorportDeviceReady after delete or detach commands.<o:p></o:p></P>
<P style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'><SPAN style="mso-list: Ignore">-<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'>NVMeGetNamespaceStatusAndSlot(pDevExt, currentNSID, &lunId); moved inside the below condition.<BR></SPAN><SPAN style='FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"'> if (pNsMgmtDW10->SEL == NAMESPACE_MANAGEMENT_DELETE) { }</SPAN><SPAN style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'><o:p></o:p></SPAN></P>
<P style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style='FONT-FAMILY: "Calibri",sans-serif'><SPAN style="mso-list: Ignore">-<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'>In function: NVMeIoctlNamespaceMgmt - allocate memory for pNsCtrlsList and free the memory after command completion</SPAN>. <o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>In the Namespace Detach/Delete path – removed unnecessary calls to StorportNotification<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>In functions NVMeCompletionNsAttachment and FormatNVMGetIdentify changed PRP preparation to size of Identify Namespace<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>In function NVMeSetFeaturesCompletion<I> </I>added check for <SPAN style='FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"'>SC==INVALID_NAMESPACE_OR_FORMAT</SPAN><o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>In function NVMeSetFeaturesCompletion<I> </I>For the case where NS Mgmt is not supported, nsStatus should be set to ATTACHED<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>In function NVMeSetFeaturesCompletion<I> </I>In the case where NS mgmt is not supported, nsStatus will be "INVALID"<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Suggested feedback I did not incorporate:<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>I was not able to make any improvements to the driver handling for the zero attached namespace case. If the feedback is that this must be implemented for this patch, I will need two more weeks. <o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN><SPAN style='FONT-SIZE: 10pt; FONT-FAMILY: "Courier New"'>pAE->DriverState.NumQueuesSet –</SPAN> I could not find any such field in the driver<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>Check should validate that the SCT is GENERIC_COMMAND_STATUS – I did not change this because I’d have to add a new else condition, and I could not commit to testing that kind of a change.<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>I didn’t make any of the suggested changes to the LBA RANGE buffer size, because again, I could not commit to testing them<o:p></o:p></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN style="mso-list: Ignore">-<SPAN style='FONT-SIZE: 7pt; FONT-FAMILY: "Times New Roman"; FONT-VARIANT: normal; FONT-STYLE: normal; LINE-HEIGHT: normal'> </SPAN></SPAN>It is safe to set SEL field to <SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Consolas">NAMESPACE_MANAGEMENT_DELETE </SPAN> in the pNsMgmtCmd structure – as far as I can see when stepping through the code we set this, line 4102 in nvmeStd.c<o:p></o:p></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal>Carolyn<o:p></o:p></P>
<P class=MsoNormal><A name=_MailEndCompose><SPAN style="COLOR: #1f497d"><o:p> </o:p></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>From:</B> nvmewin-bounces@lists.openfabrics.org [mailto:nvmewin-bounces@lists.openfabrics.org] <B>On Behalf Of </B>Foster, Carolyn D<BR><B>Sent:</B> Friday, January 15, 2016 4:57 PM<BR><B>To:</B> nvmewin@lists.openfabrics.org<BR><B>Subject:</B> [nvmewin] Patch with changes for Namespace Management<o:p></o:p></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Hi all,<o:p></o:p></P>
<P class=MsoNormal>This patch includes changes to support Namespace Management updates from the NVMe specification 1.2. This patch implements some fixes for handling non-continuous namespaces, adds handling for attached and detached namespaces, and implements new IOCTLs to create, delete, attach and detach namespaces.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I have made a detailed overview of the changes in the text file in the attached zip file, the contents are also copied here below. <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Password is intelnvme<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Please let me know if you have any questions.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Carolyn Foster<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>This patch includes changes to support Namespace management, including create, delete, <o:p></o:p></P>
<P class=MsoNormal>attach and detach namespace operations. The new functionality in this patch was tested <o:p></o:p></P>
<P class=MsoNormal>using proprietary tools. We tested on Server 2008 R2, Server 2012 R2 and Windows 8.1<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>******************<o:p></o:p></P>
<P class=MsoNormal>Design Assumptions<o:p></o:p></P>
<P class=MsoNormal>******************<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>1. The numbering of namespaces need not be consecutive.<o:p></o:p></P>
<P class=MsoNormal>2. The namespace ID can be any number between 1 and 2^32.<o:p></o:p></P>
<P class=MsoNormal>3. A namespace is considered “active” only when it is created and attached to this controller.<o:p></o:p></P>
<P class=MsoNormal>4. A detached namespace, or one that is just created but not yet attached is considered “inactive”. <o:p></o:p></P>
<P class=MsoNormal>5. A non-existent, or deleted namespace is considered “invalid”.<o:p></o:p></P>
<P class=MsoNormal>6. An active namespace will result in one (and only one) “Online” LUN.<o:p></o:p></P>
<P class=MsoNormal>7. Assuming single-host, and single-controller NVMe system.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>*********************<o:p></o:p></P>
<P class=MsoNormal>Architecture Overview<o:p></o:p></P>
<P class=MsoNormal>*********************<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>There are four new IOCTLs for namespace management, Create, Delete, Attach and Detach. An attached <o:p></o:p></P>
<P class=MsoNormal>namespace will result in a visible LUN to the Windows OS. The LUN extension table has been updated <o:p></o:p></P>
<P class=MsoNormal>to have a Namespace status:<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>typedef enum _NS_STATUS<o:p></o:p></P>
<P class=MsoNormal>{<o:p></o:p></P>
<P class=MsoNormal> INVALID = 0, //Namespace ID does not exist (not known to controller).<o:p></o:p></P>
<P class=MsoNormal> INACTIVE, //Namespace is created, but not attached to controller.<o:p></o:p></P>
<P class=MsoNormal> ATTACHED //Namespace is created and attached to controller.<o:p></o:p></P>
<P class=MsoNormal>} NS_STATUS;<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>In order to properly build the LUN extension table during initialization, we made changes to identify <o:p></o:p></P>
<P class=MsoNormal>all namespaces, and to determine each namespace’s status. These changes include new states in the <o:p></o:p></P>
<P class=MsoNormal>Init State Machine NVMeRnningWaitOnListAttachedNs and NVMeRunningWaitOnListExistingNs. The updated <o:p></o:p></P>
<P class=MsoNormal>state machine steps are as follows:<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>1. Send an Identify Namespace command with CNS set to 02h. This should return a list of all active (created and attached) namespaces.<o:p></o:p></P>
<P class=MsoNormal>2. Go through the list and update LUN extension entries accordingly, one entry for each namespace. Set all LUN status to online.<o:p></o:p></P>
<P class=MsoNormal>3. Send an Identify Namespace command with CNS set to 10h. This should return a list of all existing namespaces in the system, active and inactive.<o:p></o:p></P>
<P class=MsoNormal>4. Go through the list. <o:p></o:p></P>
<P class=MsoNormal>5. If a corresponding LUN entry exists, skip this step, as this must have been an active namespace that was covered in previous steps.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>LUN extension entries are populated as follows:<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>When a namespace is created:<o:p></o:p></P>
<P class=MsoNormal>- namespaceId is set.<o:p></o:p></P>
<P class=MsoNormal>- nsStatus is set to “INACTIVE”<o:p></o:p></P>
<P class=MsoNormal>- slotStatus is set to “FREE”<o:p></o:p></P>
<P class=MsoNormal>- identifyData is partially set<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>When a namespace is attached:<o:p></o:p></P>
<P class=MsoNormal>- drive is pulled for namespace identify<o:p></o:p></P>
<P class=MsoNormal>- identifyData is set accordingly<o:p></o:p></P>
<P class=MsoNormal>- nsStatus is set to “ATTACHED”<o:p></o:p></P>
<P class=MsoNormal>- slotStatus is set to “ONLINE”<o:p></o:p></P>
<P class=MsoNormal>- ReadOnly is set to FALSE<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>When a namespace is detached:<o:p></o:p></P>
<P class=MsoNormal>- nsStatus is set to “INACTIVE”<o:p></o:p></P>
<P class=MsoNormal>- slotStatus is set to “FREE”<o:p></o:p></P>
<P class=MsoNormal>- ReadOnly is set to TRUE<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>When a namespace is deleted:<o:p></o:p></P>
<P class=MsoNormal>- The entire LUN extension entry is set to 0.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>There are also new reasons for the LUN to be offline:<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>typedef enum _LUN_OFFLINE_REASON<o:p></o:p></P>
<P class=MsoNormal>{<o:p></o:p></P>
<P class=MsoNormal> NOT_OFFLINE,<o:p></o:p></P>
<P class=MsoNormal> FORMAT_IN_PROGRESS,<o:p></o:p></P>
<P class=MsoNormal> DETACH_IN_PROGRESS,<o:p></o:p></P>
<P class=MsoNormal> DELETE_IN_PROGRESS<o:p></o:p></P>
<P class=MsoNormal> // Add more as needed<o:p></o:p></P>
<P class=MsoNormal>} LUN_OFFLINE_REASON;<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>When delete or detach requests are made, the driver will call StorportDeviceBusy to pause incoming requests, <o:p></o:p></P>
<P class=MsoNormal>and the LUN is marked as offline with the appropriate reason. When a user tries to delete an attached namespace, <o:p></o:p></P>
<P class=MsoNormal>the driver will first send a detach command, and then the delete command. <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>*****************<o:p></o:p></P>
<P class=MsoNormal>Known Limitations<o:p></o:p></P>
<P class=MsoNormal>*****************<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>1. If no namepsaces are present, the driver will fail to load.<o:p></o:p></P>
<P class=MsoNormal>2. If an error happens on any one namespace during initialization the driver will fail to load. <o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>The handling for these two scenarios could be strengthened and improved, which we did not get to in this patch.<o:p></o:p></P></DIV></X-BODY>
<P> </P>
<P> </P>
<P> </P>
<P> </P>
<TABLE id=confidentialsignimg>
<TBODY>
<TR>
<TD NAMO_LOCK>
<P><IMG border=0 src="cid:BGFC2LL5XOK0@namo.co.kr"></P></TD></TR></TBODY></TABLE></BODY></HTML><img src='http://ext.samsung.net/mailcheck/SeenTimeChecker?do=22f8650517ba68655e9ebd4ee858fbd4c5713e275360f6b77d9badbdf7e30042d1afaaba7860cdcd9564217c646641ad61e16949eaa607501b20909a04efd4d2748cfe1d4e847419cf878f9a26ce15a0' border=0 width=0 height=0 style='display:none'>