[nvmewin] Release 1.4 Plan and schedule
Robles, Raymond C
raymond.c.robles at intel.com
Mon Jun 30 15:57:06 PDT 2014
You're welcome!
Did the attachment get blocked? It was 11MB and I got a mail delivery failure message?
From: Kwok Kong [mailto:Kwok.Kong at pmcs.com]
Sent: Monday, June 30, 2014 3:55 PM
To: Robles, Raymond C; nvmewin at lists.openfabrics.org
Subject: RE: [nvmewin] Release 1.4 Plan and schedule
Ray,
This is great that you release this example code. I'll work with Alex to check it into the nvmewin repo.
Thanks
-Kwok
From: Robles, Raymond C [mailto:raymond.c.robles at intel.com]
Sent: Monday, June 30, 2014 3:52 PM
To: Kwok Kong; nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: RE: [nvmewin] Release 1.4 Plan and schedule
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: %%SENT_DATE%%
Subject: Suspect Message Quarantined
WARNING: The virus scanner was unable to scan an attachment in an email message sent to you. This attachment could possibly contain viruses or other malicious programs. The attachment could not be scanned for the following reasons:
%%DESC%%
The full message and the attachment have been stored in the quarantine.
The identifier for this message is '%%QID%%'.
Access the quarantine at:
https://puremessage.pmc-sierra.bc.ca:28443/
For more information on PMC's Anti-Spam system:
http://pmc-intranet/wiki/index.php/Outlook:Anti-Spam_FAQ
IT Services
PureMessage Admin
Kwok,
This is great to see! Thank you to all the companies now contributing. I'm very happy to see the driver grow and evolve with the needs of the environment.
On a similar note, I recently wrote a small, sample user space application that sends pass through IOCTLs. I had been getting external requests on how to actually code pass through IOCTLs for NVMe devices. So, in the spirit of information sharing. I have attached the sample app here. This code is non-proprietary and should fall under the BSD license.
Please feel free to use, or even possibly post to the nvmewin repo so that other contributors and/or companies can pull this sample source code for reference.
Zip password: intel1234
Enjoy!
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 Kwok Kong
Sent: Monday, June 30, 2014 3:12 PM
To: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: [nvmewin] Release 1.4 Plan and schedule
All,
I am happy to announce that we now have a solid plan with commitment from a few companies to contribute to the 1.4 release of the driver by Nov 2014. Thanks to all the companies who contribute resource to make it happen. The plan is to follow as:
Code commit order and Feature By Date Note
1. Migrate to VS2013, WDK 8.1 Tom Freeman at hgst end of July
2. WHQL Certification test Alex Chang at PMC early Aug include suggestion by Samsung
3. buglist as suggested by Samsung (attached) Judy @Samsung Mid Aug
4. WPP Tracing/WMI processing Tom Freeman at hgst end of Aug
5. NVMe format enhancement Alex Chang at PMC early Sep
6. Bus reset enhancement Judy at Samsung Mid Sep
7. Hot plug/swap Judy @Samsung End of Oct
Release 1.4 will be tested with VS2013, WDK 8.1 only. Older version of the tools may work but not be verified by the working group.
Let's focus on getting release 1.4 out by Nov 2014. Go team Go.
Thanks
-Kwok
Here is the meeting note for the May 21 2014 meeting:
====== ==
NVMe OFA Windows Driver Meeting Note (May 21, 2014)
Meeting Status
==============
1. Reviewed 1.3 release
- No further comment from the group.
2. The group agreed on the following features for the 1.4 Release
- Driver Trace feature (WPP tracing) - Tom Freeman at hgst
- WMI commands processing - Tom Freeman at hgst
- Migrate to VS2013, WDK 8.1 - Tom Freeman at hgst
- WHQL Certification test - Alex Chang at PMC
- NVMe format enhancement / bug fix - Alex Chang at PMC
3. Expected release date for 1.4 is Nov 2014
4. Hot plug (graceful hot add/remove) and hot swap (surprised hot add/remove)
features were discussed. Austin bolen from Dell said that surprise hot add/remove
had been in the PCIe standard since version 1. We should support it in future
release of the driver.
We would consider adding hot plug/swap support in future release of the driver.
5. The group reviewed the bug list / new features per suggestion from Judy @ Samsung.
- We agreed that everything on the list should be fixed.
- Need volunteers to work on the fix with the 1.4 release
- Judy was going to check with her management team if she could submit patches to fix
all these problems.
Features that are not supported currently
=========================================
NVMe 1.1 support:
- multi-path
- SGL
- Get/Set feature update
- Autonomous power state transition
- Host Identifier
- Reservation Notification Mask
- Reservation Persistence
- identify structure update
- write zeros command
End to End Protection
Hot Plug (graceful hot add/remove)
Hot Swap (surprised hot add/remove)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20140630/782d88f9/attachment.html>
More information about the nvmewin
mailing list