From cheng.peng at memblaze.com  Mon Jul  6 04:58:10 2015
From: cheng.peng at memblaze.com (Cheng Peng)
Date: Mon, 6 Jul 2015 11:58:10 +0000
Subject: [nvmewin] issue a patch
Message-ID: <SH2PR01MB23398EE188781D7F79ED4CEF5930@SH2PR01MB233.CHNPR01.prod.partner.outlook.cn>

Would you merge the patch into SVN trunk？

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150706/c4f7c12b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nvmeInit.c.patch
Type: application/octet-stream
Size: 451 bytes
Desc: nvmeInit.c.patch
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150706/c4f7c12b/attachment.obj>

From premchand.patil at einfochips.com  Thu Jul  2 23:56:56 2015
From: premchand.patil at einfochips.com (Premchand Patil)
Date: Fri, 3 Jul 2015 06:56:56 +0000
Subject: [nvmewin] Device Coult Not Be Started (Code 10)
Message-ID: <HKXPR02MB0597BCB7AC89365C64A3AFD39B960@HKXPR02MB0597.apcprd02.prod.outlook.com>

Hello,


While using NVM device emulated by QEMU, device was able to be detected, configured and installed with Windows 8.1 but device could not be started with generic code as 10 and Problem as 0x15.


If anyone have more information or solution for this problem, please provide.


Log Name:      Microsoft-Windows-Kernel-PnP/Configuration
Source:        Microsoft-Windows-Kernel-PnP
Date:          7/3/2015 6:03:53 AM
Event ID:      411
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Prem
Description:
Device PCI\VEN_8086&DEV_5845&SUBSYS_11001AF4&REV_01\3&13c0b0c5&0&20 had a problem starting.

Driver Name: oem1.inf
Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}
Service: nvme
Lower Filters:
Upper Filters:
Problem: 0x15
Status: 0x0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>411</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-03T13:03:53.066221500Z" />
    <EventRecordID>205</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="164" />
    <Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
    <Computer>Prem</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DeviceInstanceId">PCI\VEN_8086&amp;DEV_5845&amp;SUBSYS_11001AF4&amp;REV_01\3&amp;13c0b0c5&amp;0&amp;20</Data>
    <Data Name="DriverName">oem1.inf</Data>
    <Data Name="ClassGuid">{4D36E97B-E325-11CE-BFC1-08002BE10318}</Data>
    <Data Name="ServiceName">nvme</Data>
    <Data Name="LowerFilters">
    </Data>
    <Data Name="UpperFilters">
    </Data>
    <Data Name="Problem">0x15</Data>
    <Data Name="Status">0x0</Data>
  </EventData>
</Event>





Thanks and Regards,

Premchand Patil.


        <https://twitter.com/einfochipsltd>
************************************************************************************************************************************************************* eInfochips Business Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated. Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. *************************************************************************************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150703/63311c14/attachment.html>

From raymond.c.robles at intel.com  Mon Jul  6 15:17:03 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Mon, 6 Jul 2015 22:17:03 +0000
Subject: [nvmewin] issue a patch
In-Reply-To: <SH2PR01MB23398EE188781D7F79ED4CEF5930@SH2PR01MB233.CHNPR01.prod.partner.outlook.cn>
References: <SH2PR01MB23398EE188781D7F79ED4CEF5930@SH2PR01MB233.CHNPR01.prod.partner.outlook.cn>
Message-ID: <49158E750348AA499168FD41D88983606B6B72F1@fmsmsx117.amr.corp.intel.com>

Hi Cheng,

Thank you for submitting a patch. The OFA NVMeWin community always welcomes and encourages contributions.

Kindly please refer to the patch submission process defined by OFA NVMeWin. The details of the patch submission process have been published on this distribution list. Here is a link to the OFA website (where there are links provided for archived list distributions).

For reference, below is the patch submission process (also attached). All of the tools required for unit testing are open and available online. If you need assistance in obtaining any of the tools, please let me know.


This is a reminder of the procedure to submit  patch:

Process:

- Submitter needs to base their changes on the latest (and re-base/re-test prior to sending their patch).
- They send the patch to the email list "nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>".
- Some review will happen over the reflector, the maintainer will send a message out that the db is locked
  when they’re ready to apply the patch which will be once at least one member from each company
  on the review panel has approved (can be via email or con call if needed).  Once the patch is applied,
  the maintainer will send an email out.

Patch contents:

- Code changes, short summary for SVN log, more verbose write up for release notes, confirmation of what Windows platforms had been tested.
- Patch must follow the coding guidelines as attached.
- All source files should be zipped up into a .zip file with password enabled. The zip file name should properly describe the main changes of the patch.

Reviews:
- Patches submitted by anyone, email to distribution list "nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>".
- Patch submission should include time sensitivity/expectations.
- Patch submission should include justification for the patch (what value will it add, and are
  tradeoffs what are they and why would we want to take a hit).  If multiple implementation
  options were considered, what data/reasoning was behind the implementation choice.
- At a minimum reviews need to be completed by Intel, PMC, HGST, and Samsung representatives.
- Reviews include compliance with coding guidelines (in SVN) as well as logic

Unit Testing:
- All patches and release candidates required, at a minimum, the following;
                - 1 hour of data integrity testing using sdstress (Microsoft Tool)
                - 1 hour of heavy stress testing using IOMETER covering, at least, 512B, 4KB and 128KB ranging
                  from 1 OIO to 64 OIO both sequential and random
                - Quick and slow format of both MBR and GPT partitioning
                - Microsoft SCSI Compliance, no failures except (warnings OK)
                - Additional testing with other tools is encouraged
                - Occurs in all supported OSs for the release
                                - 64-bit, Windows 7, 8.0, 8,1, server 2008R2 and 2012
                                - 32-bit, Windows 7, 8.0
                - Minimum test platform is latest QEMU.  Those with their HW should test on it as well.
                 QEMU is available at https://github.com/nvmeqemu/nvmeqemu


Thanks,
Ray Robles

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Cheng Peng
Sent: Monday, July 06, 2015 4:58 AM
To: nvmewin at lists.openfabrics.org
Subject: [nvmewin] issue a patch

Would you merge the patch into SVN trunk？

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150706/4795a1f1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Coding_guidelines.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 76721 bytes
Desc: Coding_guidelines.docx
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150706/4795a1f1/attachment.docx>
-------------- next part --------------
An embedded message was scrubbed...
From: "Robles, Raymond C" <raymond.c.robles at intel.com>
Subject: FW: [nvmewin]  OFA driver patch release procedure
Date: Mon, 6 Jul 2015 22:09:38 +0000
Size: 117661
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150706/4795a1f1/attachment.mht>

From raymond.c.robles at intel.com  Mon Jul  6 16:08:52 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Mon, 6 Jul 2015 23:08:52 +0000
Subject: [nvmewin] Device Coult Not Be Started (Code 10)
In-Reply-To: <HKXPR02MB0597BCB7AC89365C64A3AFD39B960@HKXPR02MB0597.apcprd02.prod.outlook.com>
References: <HKXPR02MB0597BCB7AC89365C64A3AFD39B960@HKXPR02MB0597.apcprd02.prod.outlook.com>
Message-ID: <49158E750348AA499168FD41D88983606B6B75B1@fmsmsx117.amr.corp.intel.com>

Hi Premchand,

Thanks for reaching out. First things first, your email was bounced because you are not a member of NVMeWin email distribution list. It is very easy to join, just go to the following URL and request access to join  the list. Anyone can join... and we encourage all to join and openly discuss the OFA driver.

https://www.openfabrics.org/index.php/working-groups-overview.html#nvmewin

As to your problem outlined below, unfortunately there is not enough information here to debug your issue. All the information you have provided is user space level information.

In order to properly assess, we would need either a kernel dump (full, not mini), debug print output (either from WinDbg or DebugView), or some level of information at the driver level as to what is occurring (i.e. failure in the init state machine).

Thanks,
Ray Robles

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Premchand Patil
Sent: Thursday, July 02, 2015 11:57 PM
To: nvmewin at lists.openfabrics.org
Subject: [nvmewin] Device Coult Not Be Started (Code 10)


Hello,



While using NVM device emulated by QEMU, device was able to be detected, configured and installed with Windows 8.1 but device could not be started with generic code as 10 and Problem as 0x15.



If anyone have more information or solution for this problem, please provide.



Log Name:      Microsoft-Windows-Kernel-PnP/Configuration
Source:        Microsoft-Windows-Kernel-PnP
Date:          7/3/2015 6:03:53 AM
Event ID:      411
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      Prem
Description:
Device PCI\VEN_8086&DEV_5845&SUBSYS_11001AF4&REV_01\3&13c0b0c5&0&20 had a problem starting.

Driver Name: oem1.inf
Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}
Service: nvme
Lower Filters:
Upper Filters:
Problem: 0x15
Status: 0x0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>411</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-03T13:03:53.066221500Z" />
    <EventRecordID>205</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="164" />
    <Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
    <Computer>Prem</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DeviceInstanceId">PCI\VEN_8086&amp;DEV_5845&amp;SUBSYS_11001AF4&amp;REV_01\3&amp;13c0b0c5&amp;0&amp;20</Data>
    <Data Name="DriverName">oem1.inf</Data>
    <Data Name="ClassGuid">{4D36E97B-E325-11CE-BFC1-08002BE10318}</Data>
    <Data Name="ServiceName">nvme</Data>
    <Data Name="LowerFilters">
    </Data>
    <Data Name="UpperFilters">
    </Data>
    <Data Name="Problem">0x15</Data>
    <Data Name="Status">0x0</Data>
  </EventData>
</Event>





Thanks and Regards,

Premchand Patil.



************************************************************************************************************************************************************* eInfochips Business Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated. Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. *************************************************************************************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150706/de485544/attachment.html>

From cheng.peng at memblaze.com  Mon Jul  6 22:32:01 2015
From: cheng.peng at memblaze.com (Cheng Peng)
Date: Tue, 7 Jul 2015 05:32:01 +0000
Subject: [nvmewin] patch submission
Message-ID: <SHAPR01MB2394CC15FB752BDA7666C62F5920@SHAPR01MB239.CHNPR01.prod.partner.outlook.cn>

fix: Wait for device ready when enable adapter

It had been tested on Windows 2008 R2\Windows 2012 x64 platform

Please review it, and if you think it OK, please merge it to SVN trunk, thank you

Btw, the password of ZIP is ofa_nvme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150707/a9fe84a5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wait_for_device_ready_in_NVMeEnableAdapter.zip
Type: application/x-zip-compressed
Size: 196521 bytes
Desc: wait_for_device_ready_in_NVMeEnableAdapter.zip
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150707/a9fe84a5/attachment.bin>

From carolyn.d.foster at intel.com  Fri Jul 10 09:01:04 2015
From: carolyn.d.foster at intel.com (Foster, Carolyn D)
Date: Fri, 10 Jul 2015 16:01:04 +0000
Subject: [nvmewin] OFA Maintainer Role Coverage
Message-ID: <B3A485AFDDB1DD4598621E85E8EB67A83C0B7442@FMSMSX105.amr.corp.intel.com>

All,
I just want to let everyone know that I will be taking a short leave of absence from my role as source maintainer for the OFA NVMe Windows driver.  In my absence, Ray Robles will provide coverage for maintaining the source tree.  I will resume my role in September.

Carolyn

Carolyn Dase Foster
Intel Corp.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150710/70271c21/attachment.html>

From yun.wang at ulinktech.com  Fri Jul 24 18:00:01 2015
From: yun.wang at ulinktech.com (Yun Wang)
Date: Fri, 24 Jul 2015 18:00:01 -0700
Subject: [nvmewin] Zero Length for Security Receive and Security Send command
Message-ID: <00b101d0c675$3de1b5e0$b9a521a0$@wang@ulinktech.com>

Hi:

 

Current OFA driver doesn't allow zero length for Security Receive and
Security Send command.

 

Per NVMe spec., "Security Receive command with the Security Protocol field
set to 00h shall return information about the security protocols supported
by the controller. This command is used in the security discovery process
and is not associated with a Security Send command. Refer to SPC-4 for the
details of Security Protocol 00h and the SP Specific field". 

Per SPC-4 spec., "a transfer length of zero specifies that no data transfer
shall take place. This condition shall not be considered an error", zero
length of data transfer for Security Protocol 00h should be allowed.

On the other hand,  for some practices with other Security Protocol, zero
length will be needed, too.

 

This patch is to allow zero length of data transfer for Security Receive and
Security Send command. It has been tested over Win8.1 x64 platform and works
as expected. Please review and help merge it into the trunk.

 

The password for the attachment is nvme_sec.

 

Best Regards,

Yun Wang

ULINK Technology, Inc.

Website: www.ulinktech.com 

Office: +1(408) 446-8455 

Email:  <mailto:joseph.chen at ulinktech.com> yun.wang at ulinktech.com

 <http://www.ulinktech.com/> ulink logo 2

DISCLAIMER: The information contained in this message is confidential and
may be legally privileged. If you are not the intended recipient (or have
received this e-mail in error), please notify the sender immediately and
delete this e-mail. Any unauthorized copying, disclosure or distribution of
the contents in this e-mail is strictly forbidden.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150724/bdbfd01d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1628 bytes
Desc: not available
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150724/bdbfd01d/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zero_length_for_SecurityReceive_SecuritySend.zip
Type: application/octet-stream
Size: 187215 bytes
Desc: not available
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150724/bdbfd01d/attachment.obj>

From raymond.c.robles at intel.com  Thu Jul 30 14:25:02 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Thu, 30 Jul 2015 21:25:02 +0000
Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch
 volunteers
In-Reply-To: <CAHA74uqKWiN+jpu0OHf2_R_NqvPkVJLQ8KNJcw7QTfneogb9vg@mail.gmail.com>
References: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com>
	<49158E750348AA499168FD41D88983606B656163@fmsmsx117.amr.corp.intel.com>
	<CAHA74ur1=HKj3SOe5HvN6v+EUNgT5Sgi_07x9N7x51zV7fqKiQ@mail.gmail.com>
	<49158E750348AA499168FD41D88983606B6697AD@fmsmsx117.amr.corp.intel.com>
	<CAHA74upx9oFO51p_CzzqDD0jtAgBSLz6m8LM5S3iZA80eK_HaA@mail.gmail.com>
	<49158E750348AA499168FD41D88983606B669C18@fmsmsx117.amr.corp.intel.com>
	<CAHA74ur0q83+Xg6Fpr_9pO0JGaK1+Y1iaLSu=e=kpug4icWd-g@mail.gmail.com>
	<CAHA74uqKWiN+jpu0OHf2_R_NqvPkVJLQ8KNJcw7QTfneogb9vg@mail.gmail.com>
Message-ID: <49158E750348AA499168FD41D88983606B6EA959@fmsmsx117.amr.corp.intel.com>

Hi Iuliu,

I thought I responded to this email, but in case I didn’t….

For now, I would suggest separating the patch into smaller patches. The use of SVN is not dictated by the NVMeWin group, but rather the OFA (Open Fabrics Alliance) website, and its administrators.

If there were/are enough requests to migrate to github, I could call a meeting to discuss moving to another host website. But the process would not be quick, especially since we are starting to get patches for the end of year release.

Thanks,
Ray

From: Iuliu Rus [mailto:iuliur at google.com]
Sent: Thursday, June 25, 2015 12:06 PM
To: Robles, Raymond C
Cc: nvmewin at lists.openfabrics.org
Subject: Re: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers

Raymond, we are running the windows HCK fuzz test on the driver and it exposes several crashes. Also, on SCSIOP_START_STOP_UNIT it looks like SntiTransitionPowerState builds an io which it never submits, causing Windows to eventually reset the adapter.
Given that some of these fuzz crashes are potential security issues, we are getting ready to submit the patch next week. However it is rather big and the current patch submission process doesn't work that well. We would like to break it into separate changes, but with zipped thrunk this is not possible. Is there any way to switch this over to github so we can use pull requests instead? Or, should we do separate submissions for now?

On Tue, Jun 2, 2015 at 3:35 PM, Iuliu Rus <iuliur at google.com<mailto:iuliur at google.com>> wrote:
Raymond, given this, project we are going to wait for QEMU to accept the virtualization extensions first (http://git.infradead.org/users/kbusch/qemu-nvme.git/commit/162ec6479447abbd76308f831f36703aa3acc485), then submit our payload which includes what we previously discussed and the windows implementation for the nvme doorbell extensions.

On Fri, May 15, 2015 at 11:38 AM, Robles, Raymond C <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>> wrote:
Hi Iuliu,

The process for submitting a patch is quite simple (by design). The steps are as follows:


1.       Download the current latest trunk source via an SVN client (i.e. TortoiseSVN). I assume you’ve already done this.

2.       In the Releases folder, under a specific release, there are readme.txt files that explain the build environment needed. Insure you can compile the trunk with the recommended tool/build set.

3.       Port your changes over to the trunk.

4.       Unit test your changes on the trunk source.

5.       Run the required testing outlined in the file attached in this email and insure all tests are passing.

6.       Send an email with the trunk source zipped (with your ported changes) to this email distribution list.

7.       The three reviewing companies will review your changes and also run the tests in the file.

8.       If all looks good, then the source maintainer will merge your changes to the trunk, and create a tag.

9.       If there are any question/comments that require a modifications to you patch, then go back to step 4 after you’ve made any changes and complete the process again.

Let me know if you have any further questions. Feel free to add both patches into a single submission.

You should be able to download all tools necessary outlined in the file. Let us know if you need assistance.

Thanks,
Ray

From: Iuliu Rus [mailto:iuliur at google.com<mailto:iuliur at google.com>]
Sent: Thursday, May 14, 2015 11:02 PM

To: Robles, Raymond C
Cc: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: Re: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers

Can you please point me to the instructions on how to send the patch?
As for the free q list issue, we enabled driver verifier and under stress it bugchecked in RtlpCheckListEntry.

On Thu, May 14, 2015 at 10:52 PM, Robles, Raymond C <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>> wrote:
Hello,

We always welcome companies to submit patches for candidate features. No other company has volunteered for concurrent channels at this time. We would gladly welcome your patch at your earliest convenience. The first release for 2015 is planned for ~August/September... would you like to volunteer for this patch prior to this release?

As for a race condition synchronization fix for FreeQList, could you please describe the issue you were seeing and how you addressed it?

Thanks,
Ray

From: Iuliu Rus [mailto:iuliur at google.com<mailto:iuliur at google.com>]
Sent: Thursday, May 14, 2015 7:43 PM
To: Robles, Raymond C
Cc: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: Re: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers

Hello,
We are the google compute engine team and we already have Concurrent channels working. We're still figuring out how we can integrate between our internal repo and svn.
Do you still need this feature?
We also have a synchronization fix for a race that corrupted FreeQList.

On Thu, May 7, 2015 at 3:46 PM, Robles, Raymond C <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>> wrote:
All,

I just wanted to send out a quick update on the release plans for 2015. We’ve had two more companies volunteer to submit patches this year: Samsung (Suman) and HGST (Tom). Thank you to both companies for volunteering!

Here is the updated release plan for 2015. Unfortunately, some of the patch submissions will be a little later than originally planned. Therefore, I would like to ask the question: is everyone ok if we push the first release out until end of August to allow for more patches to be submitted? You can response publicly or just to me.

Other alternatives would include just having smaller releases at different cadences. I’m open to any ideas since there are still many requests for features that have claimed for patch submission.


2015 Release #1 (Q2/Q3 – 2015)

Feature

Description

Submitter

Date

Concurrent Channels

Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS.

<TBD>

<TBD>

Perf Opts

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.

Samsung (Suman)

End of June

Win 8.1 Timers

Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1… StorportRequestTimer() function needed.

Samsung (Suman)

End of July

CFS Bit Monitoring

CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS.

<TBD>

<TBD>

EOL - Read Only

Read only support for devices at EOL. Detection at init, hot plug, or run-time.

Samsung (Suman)

End of August

Namespace Mgmt

Namespace management - creation and deletion of namespaces.

Intel (Carolyn)

End of June

WHQL

WHQL test suite run (any bug fixes).

<TBD>

<TBD>



2015 Release #2 (Q4 – 2015)

Feature

Description

Submitter

Date

Multi-Path

Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, Reservations)

HGST (Tom)

Mid-November

RTD3

Active/idle RTD3

<TBD>

<TBD>

Temp Thresholds

Temperature thresholds (Get/Set Feature and AER trigger)

<TBD>

<TBD>

Live FW Update

Live firmware update

<TBD>

<TBD>

Atomicity

Atomicity Enhancements

<TBD>

<TBD>

Win 10

Win 10 support (push to Q4 release)

<TBD>

<TBD>

SNTL

SNTL 1.5 doc updates

HGST (Tom)

End of August

WHQL

WHQL test suite run (any bug fixes) - for each release of OFA

<TBD>

<TBD>


Thanks,
Ray

From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org> [mailto:nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org>] On Behalf Of Robles, Raymond C
Sent: Thursday, April 09, 2015 5:29 PM
To: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers

All,

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.

I would like to formally ask for volunteers for patch submissions. As of today, there are no volunteers for any of the below patches.

Intel would like to start with the volunteering… we will volunteer to provide the namespace management patch.

2015 Release #1 (Q2/Q3 – 2015)

Feature

Description

Submitter

Date

Concurrent Channels

Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS.

<TBD>

<TBD>

Perf Opts

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.

Samsung (Suman)

End of June

Win 8.1 Timers

Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1… StorportRequestTimer() function needed.

Samsung (Suman)

End of July

CFS Bit Monitoring

CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS.

<TBD>

<TBD>

EOL - Read Only

Read only support for devices at EOL. Detection at init, hot plug, or run-time.

Samsung (Suman)

End of August

Namespace Mgmt

Namespace management - creation and deletion of namespaces.

Intel (Carolyn)

End of June

WHQL

WHQL test suite run (any bug fixes).

<TBD>

<TBD>



2015 Release #2 (Q4 – 2015)

Feature

Description

Submitter

Date

Multi-Path

Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, Reservations)

HGST (Tom)

Mid-November

RTD3

Active/idle RTD3

<TBD>

<TBD>

Temp Thresholds

Temperature thresholds (Get/Set Feature and AER trigger)

<TBD>

<TBD>

Live FW Update

Live firmware update

<TBD>

<TBD>

Atomicity

Atomicity Enhancements

<TBD>

<TBD>

Win 10

Win 10 support (push to Q4 release)

<TBD>

<TBD>

SNTL

SNTL 1.5 doc updates

HGST (Tom)

End of August

WHQL

WHQL test suite run (any bug fixes) - for each release of OFA

<TBD>

<TBD>



Thanks,
Ray

Raymond C. Robles
NSG ISE Host Storage Software
Intel Corporation
Office: 480-554-2600<tel:480-554-2600>
Mobile: 480-399-0645<tel:480-399-0645>


_______________________________________________
nvmewin mailing list
nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
http://lists.openfabrics.org/mailman/listinfo/nvmewin




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/a62aacc6/attachment.html>

From raymond.c.robles at intel.com  Thu Jul 30 15:16:09 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Thu, 30 Jul 2015 22:16:09 +0000
Subject: [nvmewin] OFA NVMe Windows Driver Release Consolidation for 2015
Message-ID: <49158E750348AA499168FD41D88983606B6EAB52@fmsmsx117.amr.corp.intel.com>

All,

In 2015, we've seen a pretty severe drop-off in patch contributions up to this point in the year.  In 2014, there were many patch submissions, and I think it was likely due to many companies working towards product releases (which we've seen quite a few of this year... as well as last year). It has been great to see the ecosystem adopt NVMe.

Now that the "traffic" has slowed down on the distribution list, I've consulted with the four reviewing companies and we have decided that we will consolidate our two original releases and will have just one release for 2015. This release will happen at the end of 2015 and we will roll in all patches submitted up to this point in time. The original patch schedule is included below. Note that bug fix patches are not included in this schedule.

Code Reviewing Companies:

-          PMC Sierra

-          HGST

-          Samsung

-          Intel

Please let me know if you have any questions.

OFA 2015 Release - Feature Patch Schedule

Feature

Description

Submitter

Date

Concurrent Channels

Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS.

Google (Iulius)

<TBD>

Perf Opts

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.

Samsung (Suman)

June/July

Win 8.1 Timers

Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1... StorportRequestTimer() function needed.

Samsung (Suman)

July

EOL - Read Only

Read only support for devices at EOL. Detection at init, hot plug, or run-time.

Samsung (Suman)

August

Namespace Mgmt

Namespace management - creation and deletion of namespaces.

Intel (Ray/Carolyn)

August

SNTL

SNTL 1.5 doc updates

HGST (Tom)

August

Multi-Path

Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, Reservations)

HGST (Tom)

November

RTD3

Active/idle RTD3

<TBD>

<TBD>

Temp Thresholds

Temperature thresholds (Get/Set Feature and AER trigger)

<TBD>

<TBD>

Live FW Update

Live firmware update

<TBD>

<TBD>

Atomicity

Atomicity Enhancements

<TBD>

<TBD>

Win 10

Win 10 support (push to Q4 release)

<TBD>

<TBD>

CFS Bit Monitoring

CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS.

<TBD>

<TBD>

WHQL

WHQL test suite run (any bug fixes).

<TBD>

December/November



Thanks,
Ray

[cid:image001.png at 01CB3870.4BB88E70]
Raymond C. Robles
Non-Volatile Memory Solutions Group
Internal SSD Engineering
Intel(r) Corporation
Desk: 480.554.2600
Mobile: 480.399.0645

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/e85c5a88/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1756 bytes
Desc: image001.png
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/e85c5a88/attachment.png>

From raymond.c.robles at intel.com  Thu Jul 30 15:24:06 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Thu, 30 Jul 2015 22:24:06 +0000
Subject: [nvmewin] patch submission
In-Reply-To: <SHAPR01MB2394CC15FB752BDA7666C62F5920@SHAPR01MB239.CHNPR01.prod.partner.outlook.cn>
References: <SHAPR01MB2394CC15FB752BDA7666C62F5920@SHAPR01MB239.CHNPR01.prod.partner.outlook.cn>
Message-ID: <49158E750348AA499168FD41D88983606B6EABB6@fmsmsx117.amr.corp.intel.com>

Reviewing Companies,

Please provide any review comments and testing results before August 12th. We also have a patch from ULINK Technology after this patch.

In the meantime, Cheng could you please provide the following information about your patch:


-          Reason fix was needed.

-          Files modified and what was modified in each file.

-          How you unit tested your fix.

Thanks,
Ray

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Cheng Peng
Sent: Monday, July 06, 2015 10:32 PM
To: nvmewin at lists.openfabrics.org
Subject: [nvmewin] patch submission

fix: Wait for device ready when enable adapter

It had been tested on Windows 2008 R2\Windows 2012 x64 platform

Please review it, and if you think it OK, please merge it to SVN trunk, thank you

Btw, the password of ZIP is ofa_nvme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/0cee93c8/attachment.html>

From raymond.c.robles at intel.com  Thu Jul 30 15:25:20 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Thu, 30 Jul 2015 22:25:20 +0000
Subject: [nvmewin] Zero Length for Security Receive and Security Send
 command
In-Reply-To: <00b101d0c675$3de1b5e0$b9a521a0$@wang@ulinktech.com>
References: <00b101d0c675$3de1b5e0$b9a521a0$@wang@ulinktech.com>
Message-ID: <49158E750348AA499168FD41D88983606B6EABCD@fmsmsx117.amr.corp.intel.com>

Hi Yun,

Thank you for your patch submission. There is one patch in front of yours. Once that patch has been reviewed and approved, your patch will be reviewed next.

Thanks,
Ray

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Yun Wang
Sent: Friday, July 24, 2015 6:00 PM
To: nvmewin at lists.openfabrics.org
Subject: [nvmewin] Zero Length for Security Receive and Security Send command

Hi:

Current OFA driver doesn't allow zero length for Security Receive and Security Send command.

Per NVMe spec., "Security Receive command with the Security Protocol field set to 00h shall return information about the security protocols supported by the controller. This command is used in the security discovery process and is not associated with a Security Send command. Refer to SPC-4 for the details of Security Protocol 00h and the SP Specific field".
Per SPC-4 spec., "a transfer length of zero specifies that no data transfer shall take place. This condition shall not be considered an error", zero length of data transfer for Security Protocol 00h should be allowed.
On the other hand,  for some practices with other Security Protocol, zero length will be needed, too.

This patch is to allow zero length of data transfer for Security Receive and Security Send command. It has been tested over Win8.1 x64 platform and works as expected. Please review and help merge it into the trunk.

The password for the attachment is nvme_sec.

Best Regards,
Yun Wang
ULINK Technology, Inc.
Website: www.ulinktech.com<www.ulinktech.com%20>
Office: +1(408) 446-8455
Email: yun.wang at ulinktech.com<mailto:joseph.chen at ulinktech.com>
[ulink logo 2]<http://www.ulinktech.com/>
DISCLAIMER: The information contained in this message is confidential and may be legally privileged. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/defeb678/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1628 bytes
Desc: image001.jpg
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/defeb678/attachment.jpg>

From raymond.c.robles at intel.com  Thu Jul 30 16:19:33 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Thu, 30 Jul 2015 23:19:33 +0000
Subject: [nvmewin] OFA NVMe Windows Driver Patch Submission Process
Message-ID: <49158E750348AA499168FD41D88983606B6EAE90@fmsmsx117.amr.corp.intel.com>

Hello,

As a friendly reminder, here is the process for submitting a patch. Please let me know if you have any questions.

Process:

-          Submitter needs to base their changes on the latest (and re-base/re-test prior to sending their patch).

-          They send the patch to the email list "nvmewin at lists.openfabrics.org".

-          Some review will happen over the reflector, the maintainer will send a message out that the db is locked when they're ready to apply the patch which will be once at least one member from each mandatory reviewing company on the review panel has approved (can be via email or con call if needed). Once the patch is applied, the maintainer will send an email out.

Patch Contents:

-          Code changes, short summary for SVN log, more verbose write up for release notes, confirmation of what Windows platforms had been tested.

-          Patch must follow the coding guidelines as attached.

-          All source files should be zipped up into a .zip file with password enabled. The zip file name should properly describe the main changes of the patch.

Reviews:

-          Patches submitted by anyone, email to distribution list "nvmewin at lists.openfabrics.org".

-          Patch submission should include time sensitivity/expectations.

-          Patch submission should include justification for the patch (what value will it add, and are tradeoffs what are they and why would we want to take a hit).  If multiple implementation options were considered, what data/reasoning was behind the implementation choice.

-          Patch submission should include files modified and explanation of code changes in each file.

-          At a minimum reviews need to be completed by Intel, PMC-Sierra, HGST, and Samsung representatives.

-          Reviews include compliance with coding guidelines (in SVN) as well as logic.

Unit Testing (all patches and release candidates require, at a minimum, the following testing):

-          1 hour of data integrity testing using sdstress (Microsoft Tool)

-          1 hour of heavy stress testing using IOMETER covering, at least, 512B, 4KB and 128KB ranging from 1 OIO to 64 OIO both sequential and random

-          Quick and slow format of both MBR and GPT partitioning

-          Microsoft SCSI Compliance, no failures except (warnings OK)

-          Additional testing with other tools is encouraged

-          Occurs in all supported OSs for the release

o    64-bit, Windows 7, 8.0, 8,1, server 2008R2 and 2012

o    32-bit, Windows 7, 8.0

-          Minimum test platform is latest QEMU.  Those with their HW should test on it as well.

-          QEMU is available at https://github.com/nvmeqemu/nvmeqemu

Thanks,
Ray

[cid:image001.png at 01CB3870.4BB88E70]
Raymond C. Robles
Non-Volatile Memory Solutions Group
Internal SSD Engineering
Intel(r) Corporation
Desk: 480.554.2600
Mobile: 480.399.0645

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/1310afcb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1756 bytes
Desc: image001.png
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150730/1310afcb/attachment.png>

From abhijit.khande at gmail.com  Thu Jul 30 18:57:06 2015
From: abhijit.khande at gmail.com (Abhijit Khande)
Date: Fri, 31 Jul 2015 07:27:06 +0530
Subject: [nvmewin] Amy way to avoid loading inbox NVMe driver in WINPE
Message-ID: <CAF5Wg=6y+1E5N1KUW=Pfd0b5oE+yZgujRN1M-LFnhc3M+zwf6w@mail.gmail.com>

Hi All,

Is there any way to avoid loading inbox NVMe driver in WINPE during OS
installation?
Currently after booting in WINPE the class/sub-class code matched and inbox
NVMme claims the device and PDOs gets exposesed  to class driver.

Any way to avoid this stack getting buildup using by inbox driver and load
our driver.

Thanks,
AK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150731/de7249dc/attachment.html>

From raymond.c.robles at intel.com  Fri Jul 31 11:37:22 2015
From: raymond.c.robles at intel.com (Robles, Raymond C)
Date: Fri, 31 Jul 2015 18:37:22 +0000
Subject: [nvmewin] patch submission
In-Reply-To: <49158E750348AA499168FD41D88983606B6EABB6@fmsmsx117.amr.corp.intel.com>
References: <SHAPR01MB2394CC15FB752BDA7666C62F5920@SHAPR01MB239.CHNPR01.prod.partner.outlook.cn>
	<49158E750348AA499168FD41D88983606B6EABB6@fmsmsx117.amr.corp.intel.com>
Message-ID: <49158E750348AA499168FD41D88983606B6EB60E@fmsmsx117.amr.corp.intel.com>

Hi Cheng,

I've reviewed your code and have some questions.

It looks like NVMeWaitForCtrlRDY is added in init and reset path.  Previously controller ready wait is  performed in passive init path. I did not see any benefit of adding NVMeWaitForCtrlRDY in init path (I feel, old passive init path wait will be right approach to have minimal processor usage).

Could you please provide an explanation on why you moved wait for controller ready to init path?

Thanks,
Ray

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Robles, Raymond C
Sent: Thursday, July 30, 2015 3:24 PM
To: nvmewin at lists.openfabrics.org; Cheng Peng
Subject: Re: [nvmewin] patch submission

Reviewing Companies,

Please provide any review comments and testing results before August 12th. We also have a patch from ULINK Technology after this patch.

In the meantime, Cheng could you please provide the following information about your patch:


-          Reason fix was needed.

-          Files modified and what was modified in each file.

-          How you unit tested your fix.

Thanks,
Ray

From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org> [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Cheng Peng
Sent: Monday, July 06, 2015 10:32 PM
To: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: [nvmewin] patch submission

fix: Wait for device ready when enable adapter

It had been tested on Windows 2008 R2\Windows 2012 x64 platform

Please review it, and if you think it OK, please merge it to SVN trunk, thank you

Btw, the password of ZIP is ofa_nvme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150731/aecfab96/attachment.html>