<div dir="ltr"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">Hi Brandon,</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">Please find my answer below -</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">a. EoL: Detection during device hot plug - </span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">During driver initialization, the SMART/Health Information, Critical Warning field, bit 3 which mentions "If set to '1', then the media has been placed in read only mode" is the trigger to enter Read Only mode.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">In driver, we have introduced a new state in NVMeRunning(), which sends a Get Log Page for SMART Health information, and save the critical warning field. During disk initialization, when kernel sends the SCSI mode sense command with Page code 0x3f(Return all pages), in the mode parameter header, in Device specific parameter, the WP(write protect) bit is set to 1. Once the mode sense response is returned, the disk in the disk manager is shown as 'Read Only' and no more write commands are sent to the device.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">b. EoL: Detection during run time - </span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">During run time, for write command, the completion entry with SCT = 1h (Command Specific Status) and SC = 82h (Attempted Write to Read Only Range) is the trigger to enter Read Only mode. Please note that this is currently not part of the NVM Express: SCSI Translation Reference specification and is in the process of being included.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">In driver, for any write command, in the completion entry, if SCT = 1h and SC = 82h, the following sense data is returned to the kernel:</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">SrbStatus = SRB_STATUS_ERROR</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">StatusCode = SCSISTAT_CHECK_CONDITION</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">SenseKey = SCSI_SENSE_DATA_PROTECT</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">ASC = SCSI_ADSENSE_WRITE_PROTECT</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">ASCQ = SCSI_ADSENSE_NO_SENSE</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">For which the kernel sends the mode sense with Page code 0x3f, which is translated to Get log page for SMART Health information, which returns critical warning field, with bit 3 set to 1. In response to the mode sense command, in mode parameter header, in Device specific parameter, the WP(write protect) bit is set. After the mode sense response is returned, the disk in the disk manager is shown as 'Read Only' and no more write commands are sent to the device.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">We have tested this implementation in following ways - </span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">1. Insert a RO device and start the PC. After PC is booted, the disk is shown as Read Only in disk management.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">2. Hot inserted the RO device and disk management shows disk are Read Only.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">3. Executed IOmeter on the NVMe disk. Once the disk become Read Only, The 'Error Count' field in IOmeter start increases and IOPs starts dropping. Disk managements shows disk as Read Only.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">4. Tried copying files to Read Only drive and got pop up messages as Drive is write protected.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">5. When the Available Spare field in the SMART information log is 10%, started copying files to the disk. And when disk becomes Read Only, got pop up message as Driver has become write protected.</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">Thanks,</span><div><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px">Suman</span><br style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><div><span style="color:rgb(0,0,0);font-family:Arial,arial;font-size:12px"><br></span></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 15, 2015 at 12:30 AM, <span dir="ltr"><<a href="mailto:nvmewin-request@lists.openfabrics.org" target="_blank">nvmewin-request@lists.openfabrics.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send nvmewin mailing list submissions to<br>
<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin" target="_blank">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:nvmewin-request@lists.openfabrics.org">nvmewin-request@lists.openfabrics.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:nvmewin-owner@lists.openfabrics.org">nvmewin-owner@lists.openfabrics.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of nvmewin digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: nvmewin Digest, Vol 40, Issue 3 (Brandon Schulz)<br>
2. Re: nvmewin (Tom Fones-SSI)<br>
3. Re: nvmewin (Robles, Raymond C)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 13 Apr 2015 21:01:16 +0000<br>
From: Brandon Schulz <<a href="mailto:brandon.schulz@hgst.com">brandon.schulz@hgst.com</a>><br>
To: suman prakash <<a href="mailto:suman.p@samsung.com">suman.p@samsung.com</a>>,<br>
"<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>" <<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>><br>
Subject: Re: [nvmewin] nvmewin Digest, Vol 40, Issue 3<br>
Message-ID:<br>
<<a href="mailto:BN1PR0401MB09316D3E00BDAD9B0F65B9D3F2E70@BN1PR0401MB0931.namprd04.prod.outlook.com">BN1PR0401MB09316D3E00BDAD9B0F65B9D3F2E70@BN1PR0401MB0931.namprd04.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Suman -<br>
<br>
Do you know what you are going to use as a trigger for entering read-only mode at drive EOL?<br>
<br>
Brandon<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a> [mailto:<a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a>] On Behalf Of suman prakash<br>
Sent: Friday, April 10, 2015 7:39 AM<br>
To: <a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
Subject: Re: [nvmewin] nvmewin Digest, Vol 40, Issue 3<br>
<br>
All,<br>
<br>
Samsung would like to take up the following 3 patches -<br>
<br>
1. Feature - Optimizing driver initialization performance.<br>
Description - Instead of learning cores, use StorPortInitializePerfOpts() to get the array of MSI numbers corresponding to each logical processor and make the Llogical processor-Queue-MSIx mapping.<br>
Submitter - Samsung (Suman)<br>
Date - End of June<br>
<br>
2. Feature - Handling device surprise removal in IOCTL path using Win 8.1 Timers.<br>
Description - The existing implementation of detecting surprise removal during IO using the StorPortNotification(RequestTimerCall,..) does not work when IOCTL commands are outstanding. Starting from Windows 8 kernel,<br>
StorPortRequestTimer() is supported which handles the surprise removal in IOCTL path too. For Windows 7 kernel, this will be a limitation.<br>
Submitter - Samsung (Suman)<br>
Date - End of July<br>
<br>
3. Feature - Device EOF support (Read Only) Description - Read only support for devices at EOL. Detection at init, hot plug, or run-time.<br>
Submitter - Samsung (Suman)<br>
Date - End of August<br>
<br>
Thanks,<br>
Suman<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a><br>
[mailto:<a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a>] On Behalf Of <a href="mailto:nvmewin-request@lists.openfabrics.org">nvmewin-request@lists.openfabrics.org</a><br>
Sent: Friday, April 10, 2015 6:00 AM<br>
To: <a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
Subject: nvmewin Digest, Vol 40, Issue 3<br>
<br>
Send nvmewin mailing list submissions to<br>
<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin" target="_blank">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:nvmewin-request@lists.openfabrics.org">nvmewin-request@lists.openfabrics.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:nvmewin-owner@lists.openfabrics.org">nvmewin-owner@lists.openfabrics.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific than<br>
"Re: Contents of nvmewin digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. OFA Release Plan: Release #1 2015 -- Call for patch<br>
volunteers (Robles, Raymond C)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 10 Apr 2015 00:29:00 +0000<br>
From: "Robles, Raymond C" <<a href="mailto:raymond.c.robles@intel.com">raymond.c.robles@intel.com</a>><br>
To: "<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>" <<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>><br>
Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch<br>
volunteers<br>
Message-ID:<br>
<br>
<<a href="mailto:49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com">49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
All,<br>
<br>
As we enter Q2, I'm happy to announce that we a have a very good feature plan in place for both Q2 and Q4 releases in 2015 of the OFA driver. The list of requested features is included below for final review.<br>
<br>
I would like to formally ask for volunteers for patch submissions. As of today, there are no volunteers for any of the below patches.<br>
<br>
Intel would like to start with the volunteering... we will volunteer to provide the namespace management patch.<br>
<br>
2015 Release #1 (Q2/Q3 - 2015)<br>
<br>
Feature<br>
<br>
Description<br>
<br>
Submitter<br>
<br>
Date<br>
<br>
Concurrent Channels<br>
<br>
Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS.<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
Perf Opts<br>
<br>
Instead of learning cores, use perf opts. Shave off 2 seconds in init code... using Storport initialize perf opts. No need for source core interrupt steering code in driver.<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
Win 8.1 Timers<br>
<br>
Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1... StorportRequestTimer() function needed.<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
CFS Bit Monitoring<br>
<br>
CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS.<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
EOL - Read Only<br>
<br>
Read only support for devices at EOL. Detection at init, hot plug, or run-time.<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
Namespace Mgmt<br>
<br>
Namespace management - creation and deletion of namespaces.<br>
<br>
Intel (Carolyn)<br>
<br>
End of May<br>
<br>
WHQL<br>
<br>
WHQL test suite run (any bug fixes).<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
<br>
<br>
2015 Release #2 (Q4 - 2015)<br>
<br>
Feature<br>
<br>
Description<br>
<br>
Submitter<br>
<br>
Date<br>
<br>
Multi-Path<br>
<br>
Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing,<br>
Reservations)<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
RTD3<br>
<br>
Active/idle RTD3<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
Temp Thresholds<br>
<br>
Temperature thresholds (Get/Set Feature and AER trigger)<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
Live FW Update<br>
<br>
Live firmware update<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
Atomicity<br>
<br>
Atomicity Enhancements<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
Win 10<br>
<br>
Win 10 support (push to Q4 release)<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
SNTL<br>
<br>
SNTL 1.5 doc updates<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
WHQL<br>
<br>
WHQL test suite run (any bug fixes) - for each release of OFA<br>
<br>
<TBD><br>
<br>
<TBD><br>
<br>
<br>
<br>
Thanks,<br>
Ray<br>
<br>
[cid:image001.png@01CB3870.4BB88E70]<br>
Raymond C. Robles<br>
NSG ISE Host Storage Software<br>
Intel Corporation<br>
Office: 480-554-2600<br>
Mobile: 480-399-0645<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f51
9/attachment.html" target="_blank">http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f51<br>
9/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.png<br>
Type: image/png<br>
Size: 1756 bytes<br>
Desc: image001.png<br>
URL:<br>
<<a href="http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f51
9/attachment.png" target="_blank">http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f51<br>
9/attachment.png</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
nvmewin mailing list<br>
<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
<a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin" target="_blank">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><br>
<br>
<br>
End of nvmewin Digest, Vol 40, Issue 3<br>
**************************************<br>
<br>
_______________________________________________<br>
nvmewin mailing list<br>
<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
<a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin" target="_blank">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 13 Apr 2015 21:36:35 +0000<br>
From: Tom Fones-SSI <<a href="mailto:tom.fones@ssi.samsung.com">tom.fones@ssi.samsung.com</a>><br>
To: suman prakash <<a href="mailto:suman.p@samsung.com">suman.p@samsung.com</a>>,<br>
"<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>" <<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>><br>
Subject: Re: [nvmewin] nvmewin<br>
Message-ID:<br>
<<a href="mailto:EEAA00CCA2889D429E22F360CC0B0DC105C868@SSIEXCH-MB3.ssi.samsung.com">EEAA00CCA2889D429E22F360CC0B0DC105C868@SSIEXCH-MB3.ssi.samsung.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
<br>
May I ask the community if anyone has tried to install and use a custom storage class driver<br>
(replacement for Disk.sys in Windows) on an NVMe disk, and if so have they had any success ?<br>
<br>
Thanks in advance,<br>
Tom Fones @ Samsung<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 13 Apr 2015 23:01:03 +0000<br>
From: "Robles, Raymond C" <<a href="mailto:raymond.c.robles@intel.com">raymond.c.robles@intel.com</a>><br>
To: 'Tom Fones-SSI' <<a href="mailto:tom.fones@ssi.samsung.com">tom.fones@ssi.samsung.com</a>>, suman prakash<br>
<<a href="mailto:suman.p@samsung.com">suman.p@samsung.com</a>>, "<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>"<br>
<<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a>><br>
Subject: Re: [nvmewin] nvmewin<br>
Message-ID:<br>
<<a href="mailto:49158E750348AA499168FD41D88983606B636AC9@fmsmsx117.amr.corp.intel.com">49158E750348AA499168FD41D88983606B636AC9@fmsmsx117.amr.corp.intel.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
I have not heard of any such experiments.<br>
<br>
Thanks,<br>
Ray<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a> [mailto:<a href="mailto:nvmewin-bounces@lists.openfabrics.org">nvmewin-bounces@lists.openfabrics.org</a>] On Behalf Of Tom Fones-SSI<br>
Sent: Monday, April 13, 2015 2:37 PM<br>
To: suman prakash; <a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
Subject: Re: [nvmewin] nvmewin<br>
<br>
<br>
May I ask the community if anyone has tried to install and use a custom storage class driver (replacement for Disk.sys in Windows) on an NVMe disk, and if so have they had any success ?<br>
<br>
Thanks in advance,<br>
Tom Fones @ Samsung<br>
_______________________________________________<br>
nvmewin mailing list<br>
<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
<a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin" target="_blank">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
nvmewin mailing list<br>
<a href="mailto:nvmewin@lists.openfabrics.org">nvmewin@lists.openfabrics.org</a><br>
<a href="http://lists.openfabrics.org/mailman/listinfo/nvmewin" target="_blank">http://lists.openfabrics.org/mailman/listinfo/nvmewin</a><br>
<br>
<br>
End of nvmewin Digest, Vol 40, Issue 5<br>
**************************************<br>
</blockquote></div><br></div>