From Bill at Mellanox.com Tue May 5 19:48:18 2015 From: Bill at Mellanox.com (Bill Lee) Date: Wed, 6 May 2015 02:48:18 +0000 Subject: [nvmewin] OpenFabrics Alliance websit back online Message-ID: All, I wanted to let you all know that the OpenFabrics website is back up. The site had been down for a few weeks due to some corrupted code. Rather than rebuild the site we decided to upgrade the security and update the overall structure. The site now services four categories of audiences. Take a look at the home page for a complete description. The working group portal has been complete revised to help you find what you are looking for in a click or two. The next project will be to revise the structure of the OpenFabrics software download portal. Please visit the site at your earliest convenience and let me know what you think. I want to thank Ken Strandberg for making the upgrade and putting up with the back and forth between the content providers. I also want to thank the content providers and reviewers for the improvements you all helped to build. Regards, Bill ----- Bill Lee Chair, Marketing Working Group The OpenFabrics Alliance +1.408.916.0022 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffrey.c.becker at nasa.gov Wed May 6 09:55:57 2015 From: jeffrey.c.becker at nasa.gov (Jeff Becker) Date: Wed, 6 May 2015 09:55:57 -0700 Subject: [nvmewin] [Ofvwg] OpenFabrics Alliance websit back online In-Reply-To: References: Message-ID: <554A479D.4020805@nasa.gov> Typo on home page - "deliverying." -jeff On 05/05/2015 07:48 PM, Bill Lee wrote: > > All, > > I wanted to let you all know that the OpenFabrics website > is back up. The site had been down for > a few weeks due to some corrupted code. Rather than rebuild the site > we decided to upgrade the security and update the overall structure. > The site now services four categories of audiences. Take a look at > the home page for a complete description. > > The working group portal has been complete revised to help you find > what you are looking for in a click or two. The next project will be > to revise the structure of the OpenFabrics software download portal. > > Please visit the site at your earliest convenience and let me know > what you think. > > I want to thank Ken Strandberg for making the upgrade and putting up > with the back and forth between the content providers. I also want to > thank the content providers and reviewers for the improvements you all > helped to build. > > Regards, > > Bill > > ----- > > Bill Lee > > Chair, Marketing Working Group > > The OpenFabrics Alliance > > +1.408.916.0022 > > > > _______________________________________________ > ofvwg mailing list > ofvwg at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/ofvwg -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Thu May 7 15:03:13 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Thu, 7 May 2015 22:03:13 +0000 Subject: [nvmewin] NVMe device unable to started In-Reply-To: <09EF53DC-0E6E-4FCC-99E7-90A735273BAE@gmail.com> References: <45DC73B6-C776-41CF-BDD7-52FDD1EF7706@gmail.com> <49158E750348AA499168FD41D88983606B64ECDD@fmsmsx117.amr.corp.intel.com> <6B417037-CF21-4097-92F7-EE30CE4E4B5A@gmail.com> <49158E750348AA499168FD41D88983606B64F292@fmsmsx117.amr.corp.intel.com> <09EF53DC-0E6E-4FCC-99E7-90A735273BAE@gmail.com> Message-ID: <49158E750348AA499168FD41D88983606B65609E@fmsmsx117.amr.corp.intel.com> Hi Jeremy, In your output below, there are several NVMe driver print statements. I’ve highlighted and called out some important details. A couple of things I noticed in the output: - It appears you are coming out of hibernate (multiphase resume). Why is this? Is this on Win 8 or 8.1? If so, did you disable fast startup/shutdown to ensure that you are doing a full shutdown when you power off your system? - It appears the NVMe device numerated properly. - A WMI request is sent to the drive. However, the OFA driver does not handle WMI commands. Did you add WMI support? Thanks, Ray From: Cheng-Kuan Tsai [mailto:jeremy.tsai.911 at gmail.com] Sent: Tuesday, April 28, 2015 3:58 PM To: Robles, Raymond C Cc: nvmewin at lists.openfabrics.org Subject: Re: [nvmewin] NVMe device unable to started Hi, Sir Before re-installing the NVMe driver and reboot, DebugView is configured with Capture verbose kernel outputs and Log boot. The following outputs are captured by DebugView after reboot. There are some more outputs after the line, WskKnrInit, but seems nothing to do with the NVMe or STORMINI. I also borrowed an Intel SSD with NVMe support. The device works well, recognized and can be formatted. Hope this log will help. Thanks. 00000001 0.00000000 00000002 0.00000030 Copyright(C) Intel Corporation 1994-2012 00000003 0.00000060 Intel Rapid Storage Technology 12.0.1.1018 00000004 0.00002234 iastora::DriverEntry: MultiPhaseResume: ENABLED 00000005 0.02770679 9531250 - STORMINI: alloc: TotalBytesAllocated: 176 Size: 176 VirtStart: FFFFE00151DC8B40 VirtEnd: FFFFE00151DC8BF0 00000006 0.02771071 9531250 - STORMINI: alloc: TotalBytesAllocated: 560 Size: 384 VirtStart: FFFFE00151DBD010 VirtEnd: FFFFE00151DBD190 00000007 0.02870478 9531250 - STORMINI: alloc: TotalBytesAllocated: 3104 Size: 2544 VirtStart: FFFFE00151EC9010 VirtEnd: FFFFE00151EC9A00 00000008 0.02875368 9531250 - STORMINI: alloc: TotalBytesAllocated: 37392 Size: 34288 VirtStart: FFFFE00151E79000 VirtEnd: FFFFE00151E815F0 00000009 0.02875700 9531250 - STORMINI: alloc: TotalBytesAllocated: 37568 Size: 176 VirtStart: FFFFE00151DC3DD0 VirtEnd: FFFFE00151DC3E80 00000010 0.02877270 9531250 - STORMINI: alloc: TotalBytesAllocated: 828096 Size: 790528 VirtStart: FFFFE00154400000 VirtEnd: FFFFE001544C1000 00000011 0.02877874 9531250 - STORMINI: alloc: TotalBytesAllocated: 828272 Size: 176 VirtStart: FFFFE00151E1AF50 VirtEnd: FFFFE00151E1B000 00000012 0.02878236 9531250 - STORMINI: alloc: TotalBytesAllocated: 1618800 Size: 790528 VirtStart: FFFFE001544C1000 VirtEnd: FFFFE00154582000 00000013 0.02878810 9531250 - STORMINI: alloc: TotalBytesAllocated: 1618976 Size: 176 VirtStart: FFFFE00151DCA610 VirtEnd: FFFFE00151DCA6C0 00000014 0.02879142 9531250 - STORMINI: alloc: TotalBytesAllocated: 1625312 Size: 6336 VirtStart: FFFFE00151E3A000 VirtEnd: FFFFE00151E3B8C0 00000015 0.02879594 9531250 - STORMINI: alloc: TotalBytesAllocated: 1625488 Size: 176 VirtStart: FFFFE00151E005F0 VirtEnd: FFFFE00151E006A0 00000016 0.02879927 9531250 - STORMINI: alloc: TotalBytesAllocated: 1629592 Size: 4104 VirtStart: FFFFE00151E38000 VirtEnd: FFFFE00151E39008 00000017 0.02880228 9531250 - STORMINI: alloc: TotalBytesAllocated: 1629768 Size: 176 VirtStart: FFFFE00151DC3F50 VirtEnd: FFFFE00151DC4000 00000018 0.02880560 9531250 - STORMINI: alloc: TotalBytesAllocated: 1654736 Size: 24968 VirtStart: FFFFE00151E82000 VirtEnd: FFFFE00151E88188 00000019 0.03116081 9531250 - STORMINI: alloc: TotalBytesAllocated: 1655464 Size: 728 VirtStart: FFFFE00151DBCD20 VirtEnd: FFFFE00151DBCFF8 00000020 0.03116474 9531250 - STORMINI: alloc: TotalBytesAllocated: 1655472 Size: 8 VirtStart: FFFFE00151EE3220 VirtEnd: FFFFE00151EE3228 00000021 0.03116746 9531250 - STORMINI: alloc: TotalBytesAllocated: 1655480 Size: 8 VirtStart: FFFFE00152A8C080 VirtEnd: FFFFE00152A8C088 00000022 0.03117048 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656208 Size: 728 VirtStart: FFFFE00151DC5330 VirtEnd: FFFFE00151DC5608 00000023 0.03117349 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656216 Size: 8 VirtStart: FFFFE00152A9F390 VirtEnd: FFFFE00152A9F398 00000024 0.03117621 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656224 Size: 8 VirtStart: FFFFE00151EDB7D0 VirtEnd: FFFFE00151EDB7D8 00000025 0.03117923 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656952 Size: 728 VirtStart: FFFFE00151E25190 VirtEnd: FFFFE00151E25468 00000026 0.03118225 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656960 Size: 8 VirtStart: FFFFE00152A9E870 VirtEnd: FFFFE00152A9E878 00000027 0.03118497 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656968 Size: 8 VirtStart: FFFFE00152A923E0 VirtEnd: FFFFE00152A923E8 00000028 0.03118798 9531250 - STORMINI: alloc: TotalBytesAllocated: 1657696 Size: 728 VirtStart: FFFFE00151DCA7A0 VirtEnd: FFFFE00151DCAA78 00000029 0.03119100 9531250 - STORMINI: alloc: TotalBytesAllocated: 1657704 Size: 8 VirtStart: FFFFE00152A943E0 VirtEnd: FFFFE00152A943E8 00000030 0.03119372 9531250 - STORMINI: alloc: TotalBytesAllocated: 1657712 Size: 8 VirtStart: FFFFE00151F66BF0 VirtEnd: FFFFE00151F66BF8 00000031 0.03119644 9531250 - STORMINI: alloc: TotalBytesAllocated: 1658440 Size: 728 VirtStart: FFFFE00151DC1010 VirtEnd: FFFFE00151DC12E8 00000032 0.03119976 9531250 - STORMINI: alloc: TotalBytesAllocated: 1658448 Size: 8 VirtStart: FFFFE00151EDB270 VirtEnd: FFFFE00151EDB278 00000033 0.03120247 9531250 - STORMINI: alloc: TotalBytesAllocated: 1658456 Size: 8 VirtStart: FFFFE00151F857D0 VirtEnd: FFFFE00151F857D8 00000034 0.03120549 9531250 - STORMINI: alloc: TotalBytesAllocated: 1659184 Size: 728 VirtStart: FFFFE00151E2FD20 VirtEnd: FFFFE00151E2FFF8 00000035 0.03120851 9531250 - STORMINI: alloc: TotalBytesAllocated: 1659192 Size: 8 VirtStart: FFFFE00152B49F70 VirtEnd: FFFFE00152B49F78 00000036 0.03121123 9531250 - STORMINI: alloc: TotalBytesAllocated: 1659200 Size: 8 VirtStart: FFFFE00152AA2F70 VirtEnd: FFFFE00152AA2F78 00000037 0.03121515 9531250 - STORMINI: alloc: TotalBytesAllocated: 1666560 Size: 7360 VirtStart: FFFFE00151E36000 VirtEnd: FFFFE00151E37CC0 00000038 0.03122783 9531250 - STORMINI: CStatePackageMgr::reg LakeTinySkuWorkaround 0 00000039 0.03123055 9531250 - STORMINI: alloc: TotalBytesAllocated: 1674752 Size: 8192 VirtStart: FFFFE00151E34000 VirtEnd: FFFFE00151E36000 00000040 0.03124443 9531250 - STORMINI: alloc: TotalBytesAllocated: 3591912 Size: 1917160 VirtStart: FFFFE00154600000 VirtEnd: FFFFE001547D40E8 00000041 0.03131719 9531250 - STORMINI: alloc: TotalBytesAllocated: 3592088 Size: 176 VirtStart: FFFFE00151DC9550 VirtEnd: FFFFE00151DC9600 00000042 0.03132232 9531250 - STORMINI: alloc: TotalBytesAllocated: 3657632 Size: 65544 VirtStart: FFFFE00151E89000 VirtEnd: FFFFE00151E99008 00000043 0.03134888 initParms->cachedMemSize = 0x293018 (2699288) 00000044 0.03135069 initParms->nonCachedMemSize = 0x1270f0 (1208560) 00000045 0.03135220 cachedMemSize + nonCachedMemSize = 0x3ba108 (3907848) 00000046 0.03137454 9531250 - STORMINI: alloc: TotalBytesAllocated: 7565480 Size: 3907848 VirtStart: FFFFE00154800000 VirtEnd: FFFFE00154BBA108 00000047 0.03144065 initOsVersion - isOsVistaOrAbove - TRUE - Maj: 6 Min: 3 00000048 0.03144246 initOsVersion - isOsWin8OrAbove - TRUE - Maj: 6 Min: 3 00000049 0.29456350 IOINIT: Built-in driver \Driver\hwpolicy failed to initialize with status - 0xC000025E 00000050 2.34740210 32656250 - STORMINI: DsmIoctlRequest: CRASHDUMP_FILE_PROFILE: DataSetRangesCount: 1 00000051 2.34740639 32656250 - STORMINI: RANGE0: StartingOffset(Bytes): 0000000FD4D28000 LengthInBytes: 0000000220000000 00000052 2.49084306 34062500 - STORMINI: StorPortInitialize returns Status(0x0) 00000053 7.37320852 Entered WinDriver v10.11 Jungo (c) 1997 - 2010 Build Date: Jan 17 2010 x86_64 64bit SYS. 00000054 7.37326765 kernel_dbg_get_registry: kernel debugger is OFF 00000055 7.72576189 AMD KMD (kernel mode GPU driver) for Windows8, Windows7 and Vista. 00000056 8.77508736 55781250 - STORMINI: DsmIoctlRequest: HIBERNATE_FILE_PROFILE: DataSetRangesCount: 2 00000057 8.77509117 55781250 - STORMINI: RANGE0: StartingOffset(Bytes): 000000028E95E000 LengthInBytes: 00000001265C8000 00000058 8.84462643 56562500 - STORMINI: Access Range, VirtualAddr=0xFFFFD000A75A5000. 00000059 8.84464073 56562500 - STORMINI: NVMeFindAdapter: Stride Size set to 0x4 00000060 8.84468079 56562500 - STORMINI: NVMeEnumNumaCores: # of NUMA node(s) = 1. 00000061 8.84468269 56562500 - STORMINI: NVMeEnumNumaCores: Number of groups = 1. 00000062 8.84468460 56562500 - STORMINI: NVMeEnumNumaCores: Group(0) affinity mask(0xff). 00000063 8.84468746 56562500 - STORMINI: NVMeEnumNumaCores: Total 8 logical processors 00000064 8.84468842 56562500 - STORMINI: NVMeEnumNumaCores: NUMA Node#0 00000065 8.84468937 56562500 - STORMINI: Core mask is 0xff in Group(0) 00000066 8.84469223 56562500 - STORMINI: There are 8 cores in Node#0. 00000067 8.84469318 56562500 - STORMINI: The total number of CPU cores 8. 00000068 8.84481144 56562500 - STORMINI: NVMeEnumMsiMessages: Msg granted=8 00000069 8.84481812 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000070 8.84482098 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000071 8.84483242 56562500 - STORMINI: NVMeInitSubQueue : SQ 0x0 pSubTDBL 0xFFFFD000A75A6000 at index 0x0 00000072 8.84484386 56562500 - STORMINI: NVMeInitCplQueue : CQ 0x0 pCplHDBL 0xFFFFD000A75A6004 at index 0x1 00000073 8.84485054 56562500 - STORMINI: NVMeEnableAdapter: Setting EN... 00000074 8.84485340 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000075 8.84485722 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000076 8.84521294 56562500 - STORMINI: NVMeRunningWaitOnRDY: Waiting... 00000077 8.85554409 56718750 - STORMINI: NVMeRunningWaitOnRDY: RDY has been set [Robles, Raymond C] <-- CSTS.RDY has been set to 1 00000078 8.87116241 56875000 - STORMINI: NVMeGetIdentifyStructures: IDEN_CONTROLLER 00000079 8.87120914 56875000 - STORMINI: NVMeInitCallback: Driver state: 33 00000080 8.88678741 57031250 - STORMINI: NVMeGetIdentifyStructures: IDEN_NAMESPACE 00000081 8.88678837 57031250 - STORMINI: NVMeGetIdentifyStructures: Get NS INFO for NSID 0x1 tgt lun 0x0 00000082 8.88680840 57031250 - STORMINI: NVMeInitCallback: Driver state: 34 00000083 8.90500259 57187500 - STORMINI: NVMeInitCallback: Driver state: 35 00000084 8.91804981 57343750 - STORMINI: NVMeInitCallback: Driver state: 35 00000085 8.93367100 57500000 - STORMINI: NVMeInitCallback: Driver state: 35 00000086 8.93367290 57500000 - STORMINI: pLbaRangeTypeEntry type : 0x0 lun id 0 nsid 0x1 00000087 8.93367577 57500000 - STORMINI: NVMeSetFeaturesCompletion: FYI LnuExt at 0 has been cleared (NSID not visible) 00000088 8.94929790 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000089 8.94930553 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000090 8.94931602 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x0 ---> QueueID 0x1 00000091 8.94932842 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000092 8.94933510 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000093 8.94934559 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x1 ---> QueueID 0x2 00000094 8.94934750 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000095 8.94935417 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000096 8.94936466 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x2 ---> QueueID 0x3 00000097 8.94936657 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000098 8.94937325 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000099 8.94938374 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x3 ---> QueueID 0x4 00000100 8.94938564 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000101 8.94939232 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000102 8.94940281 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x4 ---> QueueID 0x5 00000103 8.94940472 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000104 8.94941139 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000105 8.94942188 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x5 ---> QueueID 0x6 00000106 8.94943237 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000107 8.94944000 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000108 8.94945049 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x6 ---> QueueID 0x7 00000109 8.94945240 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000110 8.94945908 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000111 8.94946957 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x7 ---> QueueID 0x8 00000112 8.94947147 57656250 - STORMINI: NVMeMsiMapCores: Core(0x0)Msg#(0x0) 00000113 8.94947338 57656250 - STORMINI: NVMeMsiMapCores: Core(0x1)Msg#(0x1) 00000114 8.94947433 57656250 - STORMINI: NVMeMsiMapCores: Core(0x2)Msg#(0x2) 00000115 8.94947529 57656250 - STORMINI: NVMeMsiMapCores: Core(0x3)Msg#(0x3) 00000116 8.94947720 57656250 - STORMINI: NVMeMsiMapCores: Core(0x4)Msg#(0x4) 00000117 8.94947910 57656250 - STORMINI: NVMeMsiMapCores: Core(0x5)Msg#(0x5) 00000118 8.94948006 57656250 - STORMINI: NVMeMsiMapCores: Core(0x6)Msg#(0x6) 00000119 8.94948196 57656250 - STORMINI: NVMeMsiMapCores: Core(0x7)Msg#(0x7) 00000120 8.94949150 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x1 pSubTDBL 0xFFFFD000A75A6008 at index 0x2 00000121 8.94951439 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x2 pSubTDBL 0xFFFFD000A75A6010 at index 0x4 00000122 8.94953632 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x3 pSubTDBL 0xFFFFD000A75A6018 at index 0x6 00000123 8.94955730 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x4 pSubTDBL 0xFFFFD000A75A6020 at index 0x8 00000124 8.94957924 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x5 pSubTDBL 0xFFFFD000A75A6028 at index 0xa 00000125 8.94960117 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x6 pSubTDBL 0xFFFFD000A75A6030 at index 0xc 00000126 8.94962311 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x7 pSubTDBL 0xFFFFD000A75A6038 at index 0xe 00000127 8.94964409 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x8 pSubTDBL 0xFFFFD000A75A6040 at index 0x10 00000128 8.94966602 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x1 pCplHDBL 0xFFFFD000A75A600C at index 0x3 00000129 8.94967556 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x2 pCplHDBL 0xFFFFD000A75A6014 at index 0x5 00000130 8.94968605 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x3 pCplHDBL 0xFFFFD000A75A601C at index 0x7 00000131 8.94969559 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x4 pCplHDBL 0xFFFFD000A75A6024 at index 0x9 00000132 8.94970512 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x5 pCplHDBL 0xFFFFD000A75A602C at index 0xb 00000133 8.94971752 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x6 pCplHDBL 0xFFFFD000A75A6034 at index 0xd 00000134 8.94972801 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x7 pCplHDBL 0xFFFFD000A75A603C at index 0xf 00000135 8.94973755 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x8 pCplHDBL 0xFFFFD000A75A6044 at index 0x11 00000136 8.96496868 57812500 - STORMINI: NVMeInitCallback: Driver state: 38 00000137 8.98058510 57968750 - STORMINI: NVMeInitCallback: Driver state: 38 00000138 8.99621010 58125000 - STORMINI: NVMeInitCallback: Driver state: 38 00000139 9.01183414 58281250 - STORMINI: NVMeInitCallback: Driver state: 38 00000140 9.02746010 58437500 - STORMINI: NVMeInitCallback: Driver state: 38 00000141 9.04308605 58593750 - STORMINI: NVMeInitCallback: Driver state: 38 00000142 9.05871105 58750000 - STORMINI: NVMeInitCallback: Driver state: 38 00000143 9.07434368 58906250 - STORMINI: NVMeInitCallback: Driver state: 38 00000144 9.08995247 59062500 - STORMINI: NVMeInitCallback: Driver state: 39 00000145 9.10557652 59218750 - STORMINI: NVMeInitCallback: Driver state: 39 00000146 9.12120247 59375000 - STORMINI: NVMeInitCallback: Driver state: 39 00000147 9.13682747 59531250 - STORMINI: NVMeInitCallback: Driver state: 39 00000148 9.15245247 59687500 - STORMINI: NVMeInitCallback: Driver state: 39 00000149 9.16807747 59843750 - STORMINI: NVMeInitCallback: Driver state: 39 00000150 9.18370247 60000000 - STORMINI: NVMeInitCallback: Driver state: 39 00000151 9.19933605 60156250 - STORMINI: NVMeInitCallback: Driver state: 39 00000152 9.21771336 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07970 BTL 0 0 0 00000153 9.21772003 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07970 BTL 0 0 0 00000154 9.21772194 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07970 BTL 0 0 0 00000155 9.21772575 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07940 BTL 0 0 0 00000156 9.21772861 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07940 BTL 0 0 0 00000157 9.21773148 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07940 BTL 0 0 0 00000158 9.23055840 60468750 - STORMINI: NVMeRunning: StorPortReady... 00000159 11.80643463 86250000 - STORMINI: BuildIo: SRB_FUNCTION_WMI 00000160 11.80643654 86250000 - STORMINI: NVMeStartIo: SRB_FUNCTION_WMI 00000161 11.80643940 86250000 - STORMINI: Entering DispatchWmi. WMISubFunction: 0x8 WMI Flags: 0x1 00000162 13.15415096 WERKERNELHOST: ZwOpenKey failed with scode 0xc0000034 00000163 13.15415859 WERKERNELHOST: ZwOpenKey failed with scode 0xc0000034 00000164 14.85404587 116562500 - STORMINI: DsmIoctlRequest: PAGE_FILE_PROFILE: DataSetRangesCount: 1 00000165 14.85404968 116562500 - STORMINI: RANGE0: StartingOffset(Bytes): 0000000FD4D28000 LengthInBytes: 0000000220000000 00000166 14.86392689 116718750 - STORMINI: DsmIoctlRequest: PAGE_FILE_PROFILE: DataSetRangesCount: 1 00000167 14.86393070 116718750 - STORMINI: RANGE0: StartingOffset(Bytes): 000000027C250000 LengthInBytes: 0000000010000000 00000168 15.09635735 Error[PP_PowerPlay]: processpptables.c[974] -- Assertion '(0 != pTable->numEntries)' has failed: Invalid PowerPlay Table! 00000169 18.18836784 150156250 - STORMINI: CStatePackageMgr: set power scheme callback is called 00000170 22.18370628 +++++>WskKnrInit. Regard Robles, Raymond C > 於 2015年4月24日 23:49 寫道： If you are using WinDbg, you will have to enable prints for Storport Miniports. The command is ed KD_STORMINIPORT_MASK 0xf For DebugView, you shouldn’t have to modify any settings. But you will need to insure you set all the correct capture settings in the tool itself. Here are 2 links for reference… https://debugviewpp.wordpress.com/2014/01/04/7/ http://nutsaboutnets.com/faqs/dbgview/ Be sure you are capturing kernel output. From: GoogleCalendar [mailto:jeremy.tsai.911 at gmail.com] Sent: Friday, April 24, 2015 5:13 PM To: Robles, Raymond C Subject: Re: [nvmewin] NVMe device unable to started Hi, Thank you for your kind feedback, Sir. I have subscribed the mailing list. The device is Samsung NVMe SSD Controller 171X Express Flash NVMe XS1715, trying to install on a Win 8.1 machine. As for the memory dump and debug outputs, I couldn’t find any MEMORY.DUMP under my /Windows/ directory after I tried to duplicate the issue. Using DebugView, I saw some outputs but couldn’t find anything about NVMe devices. Is there any options or configurations I need to do before logging the debug kernel outputs? Thanks. Regards. Jeremy Robles, Raymond C > 於 2015年4月24日 11:09 寫道： Hi Jeremy, Thanks for reaching out to the OFA NVMe Windows distribution list. First off, could you please officially subscribe to the NVMe mailing list? People who are not on the mailing list are not allowed to send emails to the distribution. As the chair of the OFA NVMe Windows driver, I got the notification of your email and approved it (we get a lot of spam that I have to filter through). As for your issue, a little more information would be helpful: - What NVMe device/drive are you attempting to run? - Windows kernel event logs are not much help. To best analyze your failing scenario, we would need to see a couple of things: o A full kernel memory dump (not a mini-dump), or o The debug kernel output (this can either be form WinDbg or a program like DebugView). Basically what we would need is the print statements from the driver trying to load. If you could provide this info, we could provide more insight into your problem? Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of GoogleCalendar Sent: Thursday, April 23, 2015 5:07 PM To: nvmewin at lists.openfabrics.org Subject: [nvmewin] NVMe device unable to started Hello, I tried to install the release 1.4, but there’s an issue causing the device unable to start. Originally, I use the standard driver from MS for the NVMe device. The device is started and recognized by the disk drive. After I updating the driver to name-1.4 driver, the community 1.0e driver, The device was not started and not recognized by the disk drive. Based on the event log I saw, I only know there’s a problem: 0x15. (firstly configured by oem73.inf, then unable to start due to name) Can you guys have any ideas about how to fix the starting failure. Or what information, Windows log I can look up into? The attached file is the Event Log, Event ID 411. Regards. Jeremy _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Thu May 7 15:46:02 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Thu, 7 May 2015 22:46:02 +0000 Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers In-Reply-To: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com> References: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com> Message-ID: <49158E750348AA499168FD41D88983606B656163@fmsmsx117.amr.corp.intel.com> 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. 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. 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). 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 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates HGST (Tom) End of August WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray From: 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 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. 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. 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). 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 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates HGST (Tom) End of August WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray [cid:image001.png at 01CB3870.4BB88E70] Raymond C. Robles NSG ISE Host Storage Software Intel Corporation Office: 480-554-2600 Mobile: 480-399-0645 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1756 bytes Desc: image001.png URL: From iuliur at google.com Thu May 14 19:42:33 2015 From: iuliur at google.com (Iuliu Rus) Date: Thu, 14 May 2015 19:42:33 -0700 Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers In-Reply-To: <49158E750348AA499168FD41D88983606B656163@fmsmsx117.amr.corp.intel.com> References: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com> <49158E750348AA499168FD41D88983606B656163@fmsmsx117.amr.corp.intel.com> Message-ID: 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> 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. > > > > > > 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. > > > > > > 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). > > > > > > > > > > *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 > > > > > > Temp Thresholds > > Temperature thresholds (Get/Set Feature and AER trigger) > > > > > > Live FW Update > > Live firmware update > > > > > > Atomicity > > Atomicity Enhancements > > > > > > Win 10 > > Win 10 support (push to Q4 release) > > > > > > SNTL > > SNTL 1.5 doc updates > > HGST (Tom) > > End of August > > WHQL > > WHQL test suite run (any bug fixes) - for each release of OFA > > > > > > > > Thanks, > > Ray > > > > *From:* 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 > *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. > > > > > > 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. > > > > > > 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). > > > > > > > > > > *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 > > > > > > Temp Thresholds > > Temperature thresholds (Get/Set Feature and AER trigger) > > > > > > Live FW Update > > Live firmware update > > > > > > Atomicity > > Atomicity Enhancements > > > > > > Win 10 > > Win 10 support (push to Q4 release) > > > > > > SNTL > > SNTL 1.5 doc updates > > HGST (Tom) > > End of August > > WHQL > > WHQL test suite run (any bug fixes) - for each release of OFA > > > > > > > > > > Thanks, > > Ray > > > > *[image: cid:image001.png at 01CB3870.4BB88E70]* > > *Raymond C. Robles* > > NSG ISE Host Storage Software > > Intel Corporation > > Office: 480-554-2600 > > Mobile: 480-399-0645 > > > > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Thu May 14 22:52:56 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Fri, 15 May 2015 05:52:56 +0000 Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers In-Reply-To: References: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com> <49158E750348AA499168FD41D88983606B656163@fmsmsx117.amr.corp.intel.com> Message-ID: <49158E750348AA499168FD41D88983606B6697AD@fmsmsx117.amr.corp.intel.com> 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] Sent: Thursday, May 14, 2015 7:43 PM To: Robles, Raymond C Cc: 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 > 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. 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. 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). 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 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates HGST (Tom) End of August WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray From: 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 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. 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. 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). 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 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates HGST (Tom) End of August WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray Raymond C. Robles NSG ISE Host Storage Software Intel Corporation Office: 480-554-2600 Mobile: 480-399-0645 _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin -------------- next part -------------- An HTML attachment was scrubbed... URL: From iuliur at google.com Thu May 14 23:01:49 2015 From: iuliur at google.com (Iuliu Rus) Date: Thu, 14 May 2015 23:01:49 -0700 Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers In-Reply-To: <49158E750348AA499168FD41D88983606B6697AD@fmsmsx117.amr.corp.intel.com> References: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com> <49158E750348AA499168FD41D88983606B656163@fmsmsx117.amr.corp.intel.com> <49158E750348AA499168FD41D88983606B6697AD@fmsmsx117.amr.corp.intel.com> Message-ID: 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> 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] > *Sent:* Thursday, May 14, 2015 7:43 PM > *To:* Robles, Raymond C > *Cc:* 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> 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. > > > > > > 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. > > > > > > 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). > > > > > > > > > > *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 > > > > > > Temp Thresholds > > Temperature thresholds (Get/Set Feature and AER trigger) > > > > > > Live FW Update > > Live firmware update > > > > > > Atomicity > > Atomicity Enhancements > > > > > > Win 10 > > Win 10 support (push to Q4 release) > > > > > > SNTL > > SNTL 1.5 doc updates > > HGST (Tom) > > End of August > > WHQL > > WHQL test suite run (any bug fixes) - for each release of OFA > > > > > > > > Thanks, > > Ray > > > > *From:* 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 > *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. > > > > > > 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. > > > > > > 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). > > > > > > > > > > *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 > > > > > > Temp Thresholds > > Temperature thresholds (Get/Set Feature and AER trigger) > > > > > > Live FW Update > > Live firmware update > > > > > > Atomicity > > Atomicity Enhancements > > > > > > Win 10 > > Win 10 support (push to Q4 release) > > > > > > SNTL > > SNTL 1.5 doc updates > > HGST (Tom) > > End of August > > WHQL > > WHQL test suite run (any bug fixes) - for each release of OFA > > > > > > > > > > Thanks, > > Ray > > > > *Raymond C. Robles* > > NSG ISE Host Storage Software > > Intel Corporation > > Office: 480-554-2600 > > Mobile: 480-399-0645 > > > > > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Fri May 15 11:38:33 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Fri, 15 May 2015 18:38:33 +0000 Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers In-Reply-To: References: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com> <49158E750348AA499168FD41D88983606B656163@fmsmsx117.amr.corp.intel.com> <49158E750348AA499168FD41D88983606B6697AD@fmsmsx117.amr.corp.intel.com> Message-ID: <49158E750348AA499168FD41D88983606B669C18@fmsmsx117.amr.corp.intel.com> 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] Sent: Thursday, May 14, 2015 11:02 PM To: Robles, Raymond C Cc: 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 > 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] Sent: Thursday, May 14, 2015 7:43 PM To: Robles, Raymond C Cc: 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 > 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. 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. 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). 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 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates HGST (Tom) End of August WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray From: 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 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. 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. 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). 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 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates HGST (Tom) End of August WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray Raymond C. Robles NSG ISE Host Storage Software Intel Corporation Office: 480-554-2600 Mobile: 480-399-0645 _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: NVME_Tools.txt URL: From suman.p at samsung.com Fri May 22 00:04:39 2015 From: suman.p at samsung.com (SUMAN PRAKASH B) Date: Fri, 22 May 2015 07:04:39 +0000 (GMT) Subject: [nvmewin] regarding slower disk format time Message-ID: An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Fri May 22 17:06:52 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Sat, 23 May 2015 00:06:52 +0000 Subject: [nvmewin] regarding slower disk format time In-Reply-To: References: Message-ID: <49158E750348AA499168FD41D88983606B681BF2@fmsmsx117.amr.corp.intel.com> Currently, I'm unaware of optimal settings for NVMe devices in general. My take on this is that the value used should be vendor specific. Meaning that each vendor's NVMe drive will have a specific value to that vendor, regardless of a generic formula. Performing the same TRIM command may take longer on some devices than others. I believe this is why the value is defined in a very specific VPD Inquiry page. Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of SUMAN PRAKASH B Sent: Friday, May 22, 2015 12:05 AM To: nvmewin at lists.openfabrics.org Subject: [nvmewin] regarding slower disk format time All, This is regarding the slower disk format time with the OFA driver compared to Inbox driver on Windows 8.1. Uma Parepalli(skhms) had raised the same concern in February. In OFA driver, the maximum number of blocks that can be de-allocated, which driver assigns in the MAXIMUM UNMAP LBA COUNT field in Inquiry - Block Limits VPD page is set to 0xFFFF, which is the maximum number of logical blocks for a read or write command. Hence during format, OFA driver gets SCSI UNMAP commands with UNMAP DATA LENGTH set to 0xFFFF at max, always. The value in MAXIMUM UNMAP LBA COUNT field in Inquiry - Block Limits VPD page has to be set to a higher value based on the logical block size, so that driver will get lesser number of SCSI Unmap commands. We have observed during quick format on a 400GB density disk, OFA driver gets ~6000 Unmap commands. For ATA devices, following is the formula to calculate the MAXIMIMUM UNMAP LBA COUNT value: The BLOCK LIMITS VPD page MAXIMUM UNMAP LBA COUNT is calculated by multiplying the value of IDENTIFY DEVICE word 105 with 4194240 (65535 blocks per LBA range × 64 LBAranges per 512-byte block). We did not find any standard way of calculating the MAXIMUM UNMAP LBA COUNT value for NVMe. The SCSI - NVMe translation spec mentions that this value should be > 0. We can set the MAXIMUM UNMAP LBA COUNT value to the maximum possible length in logical blocks i.e, 0xFFFF_FFFF. With this, the format performance is as good as MS Inbox driver. But this may not work for bigger density disks as there will be risk of causing a time out while processing a Unmap command for large values of logical blocks. Does anybody have any idea on how to optimally calculate the MAXIMUM UNMAP LAB COUNT value for NVMe. Thanks, Suman [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=502122e85cbba61a0ce65e18eb501182daf257cfe78672b87d9badbdf7e30042d1afaaba7860cdcd9564217c646641ad61e16949eaa607501b20909a04efd4d2748cfe1d4e847419cf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: