"UNH-IOL发布NVMe协议兼容性测试套件v14.0"

需积分: 5 60 浏览量更新于2023-12-20 收藏 2.22MB PDF 举报

UNH-IOL协议兼容性测试套件新版本v14.0-Clean是由新罕布什尔大学互操作性实验室（UNH-IOL）推出的一款针对NVMe（Non-Volatile Memory Express）1.4技术规范的测试工具。该测试套件旨在帮助厂商和开发者验证其产品的兼容性和合规性，并确保其符合NVMe 1.4技术规范的要求。该套件于2020年7月21日进行了最后更新，由UNH–IOL NVMe Testing Service提供支持。 UNH–IOL是一个位于新罕布什尔州杜伦市的实验室，专门从事互操作性测试和服务。他们的NVMe兼容性测试服务旨在帮助厂商和开发者验证其产品的性能和符合度，并为他们提供技术支持和认证服务。通过使用UNH-IOL协议兼容性测试套件，用户可以根据NVMe 1.4技术规范对其产品进行全面的测试和验证。 UNH-IOL协议兼容性测试套件v14.0-Clean包括了一系列的测试用例和工具，用于测试NVMe 1.4技术规范中定义的各种功能和特性。这些测试用例涵盖了NVMe主机控制器、队列管理和存储介质管理等方面的测试，以确保产品在不同的应用场景下能够正常工作。此外，测试套件还提供了详细的测试报告和日志，帮助用户了解测试结果并进行产品优化。 UNH-IOL协议兼容性测试套件v14.0-Clean的目标是满足NVMe 1.4技术规范的要求，并帮助厂商和开发者确保其产品的符合度和兼容性。通过此套件的使用，用户可以节省时间和精力，同时提高其产品的可靠性和稳定性。此外，UNH-IOL还提供了专业的技术支持和咨询服务，帮助用户解决测试过程中遇到的问题和困难。总的来说，UNH-IOL协议兼容性测试套件v14.0-Clean是一款针对NVMe 1.4技术规范的全面测试工具，旨在帮助用户验证其产品的兼容性和合规性。该套件不仅包括了丰富的测试用例和工具，还提供了专业的技术支持和咨询服务，帮助用户解决测试过程中的问题。通过使用该套件，用户可以确保其产品符合NVMe 1.4技术规范的要求，并提高其产品在市场上的竞争力。

University of New Hampshire InterOperability Laboratory – NVMe Conformance Test Suite 
 
UNH–IOL NVMe Testing Service  16  NVMe Conformance Test Suite v14.0 
©2020 UNH–IOL 
 
David Woolf: 
•  Updated Appendix C.   
 
 
October 24, 2017 (Version 8.0b) 
David Woolf: 
•  Updated Appendix D to clarify test requirements designations for NVMeoF products.   
 
November 14, 2017 (Version 9.0 draft) 
David Woolf: 
1.  Updated Target Specification on cover page to be NVMe v1.3 
2.  Updated Default Test Setup diagram in Appendix A. 
3.  Updated Test 1.3 Case 5 to check the M bit.   
4.  Fixed error in Test 2.4 Case 3, where Step 1 was referred to in the Test Procedure rather than Step 2, 
also corrected the Status Code expected in Observable Result step 2 from 0x0A to 0x80. Also updated 
test to allow for DUT to report status code 0x81, since the status reported would be dependent on which 
check is performed first, accounting for NVMe v1.3 ECN 002.  
5.  Fixed error in Test 2.4 Case 6 where a Read command was indicated instead of a Write command.  
6.  Fixed error in Test 2.4 Case 6 where Step 1 was referred to in the Test Procedure rather than Step 2.  
7.  Fixed error in Test 2.4 Case 7 where a Read command was indicated instead of a Write command.  
8.  Fixed error in Test 2.4 Case 7 where Step 1 was referred to in the Test Procedure rather than Step 2. 
9.  Fixed error in Test 2.3 Case 2, 3, 4, 5, 6, 7 where a data pattern was written, this step was not necessary.  
10.  Updated Test 4.18 to allow devices to report support for NVMe v1.3. Added check to ensure that VER 
value from Identify Controller Data structure matches the value in VS.CAP.  
11.  Updated Test 2.1 Case 4 to match new requirements in NVMe 1.3 ECN 002, which eliminated the 
requirement for a DUT to report the lowest numerical value status code first.   
12.  Updated Test 2.3 Case 4 to match new requirements in NVMe 1.3 ECN 002, which eliminated the 
requirement for a DUT to report the lowest numerical value status code first.   
13.  Updated Test 2.3 Case 7 to match new requirements in NVMe 1.3 ECN 002,  which eliminated the 
requirement for a DUT to report the lowest numerical value status code first.   
14.  Updated Test 2.4 Case 4 to match new requirements in NVMe 1.3 ECN 002, which eliminated the 
requirement for a DUT to report the lowest numerical value status code first.   
15.  Updated Test 2.4 Case 7 to match new requirements in NVMe 1.3 ECN 002, which eliminated the 
requirement for a DUT to report the lowest numerical value status code first.   
16.  Updated Test 2.7 Case 3 to match new requirements in NVMe 1.3 ECN 002, which eliminated the 
requirement for a DUT to report the lowest numerical value status code first.   
17.  Updated Test 2.7 Case 5 to ensure that final READ command returns all 0’s.  
18.  Updated Test 2.1 Case 3 to better match the wording in NVMe 1.3 Figure 32.  
Removed steps in Test Procedure and Observable Results for Test 2.4 Cases 2-7 where a Read command was used 
to double check that a Write command had not caused data to be written, since those Read commands themselves 
could not be performed successfully, and those cases are also checked in Test 2.3 
 
November 28, 2017 (Version 9.0 draft) 
David Woolf: 
1.  Updated Test 1.2 Cases 1-4 Test Procedures and Observable Results to be more complete.  
2.  Updated Abbreviations section to stop using the ‘Mandatory if Supported’ nomenclature.  
3.  Updated Test 1.3 Case 4 to be  ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a  check for 
MDTS value at the beginning of the test to determine if the test is applicable to the DUT or not.  
4.  Updated Test 1.6 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for OACS field 
at the beginning of the test to determine if the test is applicable to the DUT or not.  
5.  Updated Test 2.1 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for ONCS field 
at the beginning of the test to determine if the test is applicable to the DUT or not.  
6.  Updated Test 2.2 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for ONCS field 
at the beginning of the test to determine if the test is applicable to the DUT or not.  

University of New Hampshire InterOperability Laboratory – NVMe Conformance Test Suite

UNH–IOL NVMe Testing Service 17 NVMe Conformance Test Suite v14.0

7. Updated Test 2.3 Case 4 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for

MDTS value at the beginning of the test to determine if the test is applicable to the DUT or not.

8. Updated Test 2.3 Case 7 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for NN

value at the beginning of the test to determine if the test is applicable to the DUT or not.

9. Updated Test 2.3 Case 6 to include a check for NN value at the beginning of the test to determine if the

test is applicable to the DUT or not.

10. Updated Observable Results of Test 2.3 Case 6 to check for status code ‘Invalid Namespace or Format

(0BH).

11. Updated Test 2.4 Case 4 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for

MDTS value at the beginning of the test to determine if the test is applicable to the DUT or not.

12. Updated Test 2.4 Case 7 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for NN

value at the beginning of the test to determine if the test is applicable to the DUT or not.

13. Updated Test 2.5 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for ONCS field

at the beginning of the test to determine if the test is applicable to the DUT or not. Added checks for

MDTS and NN values where appropriate.

14. Updated Test 2.7 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for ONCS field

at the beginning of the test to determine if the test is applicable to the DUT or not. Added checks for

MDTS and NN values where appropriate.

15. Updated Test 2.7 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for NABSN

field at the beginning of the test to determine if the test is applicable to the DUT or not.

16. Updated Test 3.1 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for Metadata

Size field at the beginning of the test to determine if the test is applicable to the DUT or not.

17. Updated Test 3.2 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for DPC field

at the beginning of the test to determine if the test is applicable to the DUT or not.

18. Updated Test 3.4 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check for HMPRE

field at the beginning of the test to determine if the test is applicable to the DUT or not.

19. Updated Test 4.13 to be ‘Mandatory’ instead of ‘Mandatory if Supported’.

20. Updated Test 5.5 Case 3 to be ‘Mandatory’ instead of ‘Mandatory if Supported’.

21. Updated Test 6.4 to be ‘Mandatory’ instead of ‘Mandatory if Supported’.

22. Updated all tests in Group 7 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check in

all tests of the ONCS field to determine of the controller supports reservations.

23. Updated all tests in Group 9 to be ‘Mandatory’ instead of ‘Mandatory if Supported’. Added a check in

all tests of the OACS field to determine of the controller supports Namespace Management.

24. Updated Appendix D to remove all references to ‘Mandatory if Supported’.

25. Updated Table in Test 1.2 to contain new Features: Timestamp, Keep Alive Timer, Host Controller

Thermal Management, Non-Operational Power State Config.

26. Updated Test 2.4 Cases 8, 9, 10 to remove redundant READ operation in Test Procedure.

December 4, 2017 (Version 9.0 draft)

David Woolf:

1. Updated Test 2.5 Case 5 to include more than 1 READ command to be performed after the Write

Uncorrectable command in order to ensure that all LBAs affected by the Write Uncorrectable command

are affected.

2. Updated Test 2.7 Case 5 to include more than 1 READ command to be performed after the Write Zeroes

command in order to ensure that all LBAs affected by the Write Zeroes command are affected.

December 6, 2017 (Version 9.0 draft)

David Woolf:

1. Updated Test 1.6 Case 3 to include a check of FNA Bit 2, to determine if the test case is applicable or

not.

2. Updated Test 1.1 Case 5, to show that CNS reserved value testing should check only FFh.

December 12, 2017 (Version 9.0 draft)

David Woolf:

University of New Hampshire InterOperability Laboratory – NVMe Conformance Test Suite

UNH–IOL NVMe Testing Service 18 NVMe Conformance Test Suite v14.0

1. Updated Test 1.3 Case 3 to only check LID 7Fh.

2. Updated Test 1.2 Case 5 to only check SEL 111b.

3. Updated Test 2.2 Case 3, Case 4, and Case 5 to be Mandatory for NVMe Drives.

4. Updated Test 1.4 Case 10 to be Mandatory for NVMe Drives.

5. Updated Test 1.7 Case 1 to be Mandatory for NVMe Drives.

6. Updated Test 2.3 Case 11 to be Mandatory for NVMe Drives.

7. Updated Test 2.4 Case 11 to be Mandatory for NVMe Drives.

8. Updated Test 2.7 Case 9 to be Mandatory for NVMe Drives.

9. Updated Test 2.9 Case 2 to be Mandatory for NVMe Drives.

10. Updated Test 5.5 Case 6 to be Mandatory for NVMe Drives.

December 14, 2017 (Version 9.0 draft)

David Woolf:

1. Added Test 1.1 Case 6.

2. Added Test 1.10 Cases 1-8

3. Added Test 1.11 Cases 1-8

4. Added Test 1.12 Cases 1-5

5. Added Test 1.13 Cases 1-4

December 21, 2017 (Version 9.0 draft)

David Woolf:

1. Updated Observable Results in Test 3.4 Case 2 to eliminate items that can not be observed. Changed the

test status to FYI.

2. Updated Observable Results in Test 3.4 Case 3 to eliminate items that can not be observed. Changed the

test status to FYI.

January 4, 2018 (Version 9.0 draft)

David Woolf:

1. Updated all references in Group 9 from 8.11 to 8.12 to match NVMe v1.3 specification.

January 22, 2018 (Version 9.0 draft)

Colin Dorsey:

1. Added tests 8.4, 8.5, 8.6, 8.7, 8.8. Updated test procedures for test 8.2

January 23, 2018 (Version 9.0 draft)

David Woolf:

1. Updated following tests from OF-FYI to OF to indicate that they are now mandatory for NVMe-oF

products, per ICC decision: 1.1 Cases 1-2, 1.3 Cases 1-2, 1.7 Case 2, 2.5 all cases, 2.6 Case 2, 2.8, 3.3

Cases 1-4, 4.1, 4.2, 4.3, 4.4, 4.6, 4.7, 4.9, 4.10, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16, 4.17, 4.18, 5.1.

February 1, 2018 (Version 9.0 draft)

David Woolf:

1. Updated test 4.13 test procedure for clarity.

2. Updated test 3.4 Case 3 test procedure for clarity and completeness.

February 5, 2018 (Version 9.0 draft)

David Woolf:

1. Modified Case 6 to Test 1.1 to cover Namespace Identification Descriptors.

2. Added Test 1.3 Cases 11, 12, 13, 14, 15 to address Telemetry Log Pages.

March 15, 2018 (Version 9.0 draft)

David Woolf:

1. Modified Case 3 of Test 1.2 for clarity.

University of New Hampshire InterOperability Laboratory – NVMe Conformance Test Suite

UNH–IOL NVMe Testing Service 19 NVMe Conformance Test Suite v14.0

2. Modified Test 7.1 Case 2 and Test 7.2 Case 3 to include the step of performing a Reservation Acquire

command.

3. Modified Test 1.2 Case 4, there was a typo indicated DWord 10 rather than DWord 0.

May 21, 2018 (Version 10.0 draft)

David Woolf:

1. Corrected typo in Test 2.2 Case 2

August 30, 2018 (Version 10.0 Release)

David Woolf:

1. 10.0 Release

November 20, 2018 (Version 11.0 draft)

David Woolf:

1. Modified Test 1.1 Case 4 as previous version of test case was invalid.

2. Renumbered Test 1.1. Case 5 as Test 1.1 Case 13.

3. Added new Test 1.1 Case 5 (FYI).

4. Added new Test 1.1 Case 6 (FYI).

5. Added new Test 1.1 Case 7 (FYI).

6. Added new Test 1.1 Case 8 (FYI).

7. Added new Test 1.1 Case 9 (FYI).

8. Added new Test 1.1 Case 10 (FYI).

9. Added new Test 1.1 Case 11 (FYI).

10. Added new Test 1.1 Case 12 (FYI).

11. Added step to Test 1.2 Case 5 to check ONCS Bit 4 to determine if test is applicable before proceeding

with test procedure.

12. Updated Test 1.2 Cases 1-4 to check if FIDs are changeable before proceeding with test procedure.

13. Updated Test 1.3 Case 2 to allow for the case where there are no unsupported LIDs because the DUT

supports all Vendor Specific LIDs.

14. Expanded Observable Results for Test 1.3 Case 11 (FYI).

15. Added new Test 1.3 Case 16.

16. Updated Test 1.3 Case 3 to use a different value for the reserved value, now uses 0x6F instead of 0x7F.

17. Fixed typo in Test 1.3 Case 4 where the test procedure referenced steps 2 and 3 when it should reference

steps 3 and 4.

18. In Test 1.3 Case 4, the reference to the list of mandatory LIDs in the specification was changed to be a

list of the mandatory LIDs, instead of a reference.

19. Updated Test 1.3 Case 7 to perform 1000 Read/Compare operations of LBADS, 2x LBADS, and 4x

LBADS to ensure that the DUT is following the requirements on recording Data Units Read in 1000 512

Byte units, rather than just recording the number of Read operations, as some devices have been observed

to do. Added a step to record the value for LBADS.

20. Updated Test 1.3 Case 8 to perform 1000 Write operations of LBADS, 2x LBADS, and 4x LBADS to

ensure that the DUT is following the requirements on recording Data Units Written in 1000 512 Byte

units, rather than just recording the number of Write operations, as some devices have been observed to

do. Remove the Write Uncorrectable operation from this test. Added a step to record the value for

LBADS.

21. Added new Test 1.3 Case 17.

22. Updated Test 1.7 Case to expect a status of 07h Command Abort Requested if a completion queue entry

is posted. If no completion queue entry is posted the test is not applicable.

23. Updated Test 1.9 to clarify that the Set Feature command in Step 2b must be performed with the Save

bit set to 1 (SV=1).

24. Updated first 2 steps in Test 1.10 Case 1 to clarify how to ensure that no Device Self Test command is

currently in progress.

25. Updated first 2 steps in Test 1.10 Case 2 to clarify how to ensure that no Device Self Test command is

currently in progress.

University of New Hampshire InterOperability Laboratory – NVMe Conformance Test Suite

UNH–IOL NVMe Testing Service 20 NVMe Conformance Test Suite v14.0

26. Updated first 2 steps in Test 1.10 Case 3 to clarify how to ensure that no Device Self Test command is

currently in progress.

27. Updated first 2 steps in Test 1.10 Case 4 to clarify how to ensure that no Device Self Test command is

currently in progress.

28. Updated first 2 steps in Test 1.10 Case 5 to clarify how to ensure that no Device Self Test command is

currently in progress.

29. Updated first 2 steps in Test 1.10 Case 6 to clarify how to ensure that no Device Self Test command is

currently in progress.

30. Updated first 2 steps in Test 1.10 Case 7 to clarify how to ensure that no Device Self Test command is

currently in progress.

31. Updated first 2 steps in Test 1.10 Case 8 to clarify how to ensure that no Device Self Test command is

currently in progress.

32. Updated first 2 steps in Test 1.11 Case 1 to clarify how to ensure that no Device Self Test command is

currently in progress.

33. Updated first 2 steps in Test 1.11 Case 2 to clarify how to ensure that no Device Self Test command is

currently in progress.

34. Updated first 2 steps in Test 1.11 Case 3 to clarify how to ensure that no Device Self Test command is

currently in progress.

35. Updated first 2 steps in Test 1.11 Case 4 to clarify how to ensure that no Device Self Test command is

currently in progress.

36. Updated first 2 steps in Test 1.11 Case 5 to clarify how to ensure that no Device Self Test command is

currently in progress.

37. Updated first 2 steps in Test 1.11 Case 6 to clarify how to ensure that no Device Self Test command is

currently in progress.

38. Updated first 2 steps in Test 1.11 Case 7 to clarify how to ensure that no Device Self Test command is

currently in progress.

39. Updated first 2 steps in Test 1.11 Case 8 to clarify how to ensure that no Device Self Test command is

currently in progress.

40. Updated first 2 steps in Test 1.12 Case 1 to clarify how to ensure that no Device Self Test command is

currently in progress.

41. Updated first 2 steps in Test 1.12 Case 2 to clarify how to ensure that no Device Self Test command is

currently in progress.

42. Updated first 2 steps in Test 1.12 Case 3 to clarify how to ensure that no Device Self Test command is

currently in progress.

43. Updated first 2 steps in Test 1.12 Case 4 to clarify how to ensure that no Device Self Test command is

currently in progress.

44. Updated first 2 steps in Test 1.12 Case 5 to clarify how to ensure that no Device Self Test command is

currently in progress.

45. Updated first 2 steps in Test 1.13 Case 1 to clarify how to ensure that no Device Self Test command is

currently in progress.

46. Updated first 2 steps in Test 1.13 Case 2 to clarify how to ensure that no Device Self Test command is

currently in progress.

47. Updated first 2 steps in Test 1.13 Case 3 to clarify how to ensure that no Device Self Test command is

currently in progress.

48. Updated first 2 steps in Test 1.13 Case 4 to clarify how to ensure that no Device Self Test command is

currently in progress.

49. Updated Test 2.7 Case 9 to allow for an error code of 81h Invalid Protection Information, as well as 02h

Invalid Field in Command.

50. Updated Test 1.10 Case 4 Observable Results step 1 to be the following: Verify that the Device Self-test

command returns status Invalid Namespace or Format in Command.

51. Updated Test 1.11 Case 4 Observable Results step 1 to be the following: Verify that the Device Self-test

command returns status Invalid Namespace or Format in Command.

52. Updated Test 1.10 Case 6 test procedure to account for the command completion for the DST command

to be sent before the DST operation completes.

剩余286页未读，继续阅读

-飞鹤-

粉丝: 798
资源: 73

"UNH-IOL发布NVMe协议兼容性测试套件v14.0"

nvme1.4.0协议

UNH-IOL-NVMe-MI-Conformance-Test-Suite-v15.0

UNH-IOL-NVMe-ZNS-Conformance-Test-Suite-v16.0-20211020

UNH-IOL-NVMe-MI-Conformance-v18.0-2022.07.13.pdf

UNH-IOL-NVMe-MI-Conformance-v20.0-2023.07.19.pdf

UNH-IOL-NVMe-MI-Conformance-v19.0-2023.01.04.docx.pdf

UNH-IOL-NVMe-ZNS-Command-Set-Conformance-v18.0-2022.07.13.pdf

UNH-IOL-NVMe-ZNS-Command-Set-Conformance-v20.0-2023.07.19.pdf

UNH-IOL-NVMe-ZNS-Command-Set-Conformance-v19.0-2023.01.04.pdf

UNH-IOL-NVMe-PCIe-Interoperability-v20.0-2023.07.19.pdf

最新资源