ANSI INCITS 536-2016 Information Technology - Zoned Block Commands (ZBC).pdf

《ANSI INCITS 536-2016 Information Technology - Zoned Block Commands (ZBC).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 536-2016 Information Technology - Zoned Block Commands (ZBC).pdf（90页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Zoned Block Commands (ZBC)INCITS 536-2016INCITS 536-2016INCITS 536-2016American National Standardfor Information Technology Zoned Block Commands (ZBC)SecretariatInformation Technology Industry CouncilApproved December 27, 2016American

2、National Standards Institute, Inc.AbstractThis standard incorporates the requirements for devices that require writing to occur at specific locations on their media. These devices allow random reading of logical block data that is already written.Approval of an American National Standard requires re

3、view by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected intere

4、sts. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence d

5、oes not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances

6、give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or spo

7、nsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purcha

8、sers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2016 by Information Tec

9、hnology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The d

10、evelopers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply t

11、o this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any stand

12、ard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.iContentsPageFOREWORD. viINTRODUCTION . xGeneral xSCSI standards family . x1 Scope . 12 Normative references . 23 Definitions, symbols, abbreviations, and convention

13、s . 33.1 Definitions . 33.2 Symbols and abbreviations 93.2.1 Abbreviations 93.2.2 Units 93.2.3 Symbols 93.2.4 Mathematical operators 93.3 Keywords 103.4 Editorial conventions 113.5 Numeric and character conventions . 113.5.1 Numeric conventions 113.5.2 Units of measure . 123.6 Bit and byte ordering

14、133.7 Notation for state diagrams 154 Zoned Block Device Model 164.1 Zoned Block Device model introduction . 164.2 Zoned Block Device models . 184.2.1 Zoned Block Device models overview 184.2.2 Host aware zoned block device model . 194.2.3 Host managed zoned block device model 194.3 Zone attributes

15、. 194.3.1 Zone attributes summary 194.3.2 Zone Type zone attribute 204.3.3 Zone Condition zone attribute . 214.3.4 WPointer zone attribute 214.3.5 RWP Recommended zone attribute . 214.3.6 Non-Sequential Write Resources Active zone attribute 214.4 Zone type models . 224.4.1 Zone type models overview

16、224.4.2 Conventional zone model . 224.4.3 Write pointer zone models 224.4.3.1 Features common to all write pointer zones 224.4.3.1.1 Write pointer features 224.4.3.1.2 Resetting the write pointer . 244.4.3.1.3 Initialization pattern 254.4.3.2 Write pointer zone operations . 254.4.3.2.1 Write pointer

17、 zone operations overview . 254.4.3.2.2 Open zone operation . 254.4.3.2.3 Close zone operation . 264.4.3.2.4 Finish zone operation 264.4.3.2.5 Reset write pointer operation . 264.4.3.2.6 Manage open zone resources operation . 264.4.3.2.6.1 Manage open zone resources operation overview 264.4.3.2.6.2

18、Select a sequential write preferred zone 274.4.3.2.6.3 Select a sequential write required zone . 27ii4.4.3.2.7 Zoned block device modifications to SBC-4 write operations and read operations . 284.4.3.3 Sequential write preferred zone model 294.4.3.3.1 Writing in sequential write preferred zones 294.

19、4.3.3.2 Reading in sequential write preferred zones . 304.4.3.4 Sequential write required zone model . 314.4.3.4.1 Writing in sequential write required zones . 314.4.3.4.2 Reading in sequential write required zones . 324.4.3.4.3 Processing unrestricted reads in sequential write required zones . 324.

20、4.3.5 Zone condition state machine . 334.4.3.5.1 Zone condition state machine overview . 334.4.3.5.2 ZC1:Empty state 364.4.3.5.2.1 ZC1:Empty state overview . 364.4.3.5.2.2 Transition ZC1:Empty to ZC2:Implicit_Open 364.4.3.5.2.3 Transition ZC1:Empty to ZC3:Explicit_Open . 364.4.3.5.2.4 Transition ZC1

21、:Empty to ZC6:Read_Only 364.4.3.5.2.5 Transition ZC1:Empty to ZC7:Offline . 374.4.3.5.3 ZC2:Implicit_Open state 384.4.3.5.3.1 ZC2:Implicit_Open state overview . 384.4.3.5.3.2 Transition ZC2:Implicit_Open to ZC1:Empty 384.4.3.5.3.3 Transition ZC2:Implicit_Open to ZC3:Explicit_Open 384.4.3.5.3.4 Trans

22、ition ZC2:Implicit_Open to ZC4:Closed . 384.4.3.5.3.5 Transition ZC2:Implicit_Open to ZC5:Full 384.4.3.5.3.6 Transition ZC2:Implicit_Open to ZC6:Read_Only 394.4.3.5.3.7 Transition ZC2:Implicit_Open to ZC7:Offline . 394.4.3.5.4 ZC3:Explicit_Open state 404.4.3.5.4.1 ZC3:Explicit_Open state overview .

23、404.4.3.5.4.2 Transition ZC3:Explicit_Open to ZC1:Empty . 404.4.3.5.4.3 Transition ZC3:Explicit_Open to ZC4:Closed 404.4.3.5.4.4 Transition ZC3:Explicit_Open to ZC5:Full 404.4.3.5.4.5 Transition ZC3:Explicit_Open to ZC6:Read_Only 404.4.3.5.4.6 Transition ZC3:Explicit_Open to ZC7:Offline . 414.4.3.5.

24、5 ZC4:Closed state . 424.4.3.5.5.1 ZC4:Closed state overview 424.4.3.5.5.2 Transition ZC4:Closed to ZC1:Empty 424.4.3.5.5.3 Transition ZC4:Closed to ZC2:Implicit_Open . 424.4.3.5.5.4 Transition ZC4:Closed to ZC3:Explicit_Open 424.4.3.5.5.5 Transition ZC4:Closed to ZC6:Read_Only . 424.4.3.5.5.6 Trans

25、ition ZC4:Closed to ZC7:Offline 434.4.3.5.6 ZC5:Full state 444.4.3.5.6.1 ZC5:Full state overview 444.4.3.5.6.2 Transition ZC5:Full to ZC1:Empty 444.4.3.5.6.3 Transition ZC5:Full to ZC6:Read_Only 444.4.3.5.6.4 Transition ZC5:Full to ZC7:Offline 444.4.3.5.7 ZC6:Read_Only state 454.4.3.5.7.1 ZC6:Read_O

26、nly state overview . 454.4.3.5.7.2 Transition ZC6:Read_Only to ZC7:Offline . 454.4.3.5.8 ZC7:Offline state 464.5 Zoned block device extensions to block device model . 464.5.1 Zoned block device internal resource management . 464.5.2 Unexpected power removal 464.5.3 Media failure . 474.6 Format opera

27、tions 474.7 Sanitize operations . 484.8 Reservations 494.9 Caches . 504.9.1 Caches overview 504.9.2 Write caching 50iii4.9.3 Command interactions with caches 504.9.4 Write operation and write medium operation interactions with caches . 504.9.5 Close zone and finish zone operation interactions with c

28、ache .505 Commands for zoned block devices 515.1 Commands for zoned block devices overview . 515.2 CLOSE ZONE command . 535.3 FINISH ZONE command 545.4 OPEN ZONE command . 555.5 READ CAPACITY (16) command 575.5.1 READ CAPACITY (16) command overview 575.5.2 READ CAPACITY (16) parameter data 575.6 REP

29、ORT ZONES command 595.6.1 REPORT ZONES command introduction . 595.6.2 REPORT ZONES parameter data 615.7 RESET WRITE POINTER command . 656 Parameters for zoned block devices 666.1 Diagnostic parameters . 666.2 Log parameters 676.3 Mode parameters . 686.4 Vital product data (VPD) parameters . 696.4.1

30、VPD parameters overview 696.4.2 Zoned Block Device Characteristics VPD page 70Annex A (Informative) Application Client Considerations for Zoned Devices 72A.1 Application client considerations for zoned devices overview 72A.2 Writing to write pointer zones . 72A.3 Open zone considerations . 72A.3.1 O

31、pen zone considerations overview . 72A.3.2 Explicitly opened zones and implicitly opened zones . 73A.3.3 Opening and closing zones 73A.3.4 Finish zone operation considerations . 73A.4 Open zone resources considerations based on zone type 74A.4.1 Sequential write preferred zones 74A.4.2 Sequential wr

32、ite required zones . 74A.5 Partial failures 75A.5.1 Partial failures overview 75A.5.2 Sanitize considerations 75Annex B (informative) Bibliography 76ivTablesPageTable 1 Numbering conventions . 12Table 2 Comparison of decimal prefixes and binary prefixes . 13Table 3 Example of ordering of bits and by

33、tes within a data dword . 14Table 4 Example of ordering of bits and bytes within an element dword . 14Table 5 Zoned block device model topics 16Table 6 Requirements of zoned block devices . 18Table 7 Summary of zone attributes 19Table 8 Zone Type zone attribute 20Table 9 Relationships between zone a

34、ttributes 20Table 10 Zone Condition zone attribute . 21Table 11 Summary of write pointer zone operations 25Table 12 Characteristics associated with zone state 34Table 13 ZBC commands that are allowed in the presence of various reservations 49Table 14 Commands for host managed zoned block devices 51T

35、able 15 CLOSE ZONE command 53Table 16 FINISH ZONE command . 54Table 17 OPEN ZONE command 55Table 18 READ CAPACITY (16) parameter data . 57Table 19 RC BASIS field . 58Table 20 REPORT ZONES command . 59Table 21 REPORT ZONES REPORTING OPTIONS field 60Table 22 REPORT ZONES parameter data . 61Table 23 SA

36、ME field description 62Table 24 Zone descriptor format 63Table 25 Zone descriptor ZONE TYPE field 63Table 26 Zone descriptor ZONE CONDITION field 64Table 27 RESET WRITE POINTER command 65Table 28 Diagnostic page codes for host managed zoned block devices 66Table 29 Log page codes and subpage codes f

37、or host managed zoned block devices 67Table 30 Mode page codes and subpage codes for host managed zoned block devices . 68Table 31 VPD page codes for zoned block devices . 69Table 32 Zoned Block Device Characteristics VPD page 70vFiguresPageFigure 0 SCSI document structure . xFigure 1 Example state

38、diagram 15Figure 2 Zones in a zoned block device . 18Figure 3 Write pointer zone and write pointer after reset write pointer operation with no subsequent writes 23Figure 4 Write pointer zone and write pointer 23Figure 5 Write pointer zone example operations 24Figure 6 Example write command that star

39、ts at the write pointer . 29Figure 7 Examples of write commands that do not start at the write pointer 30Figure 8 Zone condition state machine 35viForeword (This foreword is not part of American National Standard INCITS 536-2016.)The purpose of this standard is to define the model and command set ex

40、tensions tobe used in conjunction with the SCSI Primary Command Set standard - 5 (SPC-5)and the SCSI Block Commands - 4 (SBC-4) to facilitate operation of zoned block de-vices.This standard contains two annexes, both of which are informative and are not part ofthis standard.Requests for interpretati

41、on, suggestions for improvement and addenda, or defect re-ports are welcome. They should be sent to the INCITS Secretariat, InternationalCommittee for Information Technology Standards, Information Technology IndustryCouncil, Suite 610, 1101 K Street, NW, Washington, DC 20005.This standard was proces

42、sed and approved for submittal to ANSI by the InternationalCommittee for Information Technology Standards (INCITS). Committee approval ofthe standard does not necessarily imply that all committee members voted for ap-proval. At the time it approved this standard, INCITS had the following members:Phi

43、lip Wennblom, ChairDonald Deutsch, Vice-ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. Scott FosheeSteve Zilles (Alt.)AIM Global, Inc. Steve HallidayMary Lou Bosco (Alt.)Chuck Evanhoe (Alt.)Dan Kimball (Alt.)Apple Helene WorkmanMarc Braner (Alt.)Vir

44、ginia Fournier (Alt.)David Singer (Alt.)Department of Commerce - NIST. Michael HoganWo Chang (Alt.)Sal Francomacaro (Alt.)Farance, Inc. Frank Farance Timothy Schoechle (Alt.)Futurewei Technologies, Inc. . Yi ZhaoWilbert Adams (Alt.)Wael Diab (Alt.)GS1GO. Charles BissAndrew Hearn (Alt.)Edward Merrill

45、 (Alt.)Hewlett-Packard Enterprise Joel Fleck IIHP, Inc Karen Higginbottom Paul Jeran (Alt.)IBM Corporation Steve HolbrookAlexander Tarpinian (Alt.)IEEE . Jodi HaaszVictoria Kuperman-Super (Alt.)Don Wright (Alt.)Intel Corporation. Philip Wennblom Stephen Balogh (Alt.)Grace Wei (Alt.)Microsoft Corpora

46、tion . Laura Lindsay John Calhoon (Alt.)viiOrganization Represented Name of RepresentativeOracle CorporationDonald R. Deutsch Anish Karmarkar (Alt.)Michael Kavanaugh (Alt.)Peter Lord (Alt.)Jim Melton (Alt.)Jan-Eike Michels (Alt.)Toshihiro Suzuki (Alt.)Telecommunications Industry Association (TIA) .F

47、lorence OtienoStephanie Montgomery (Alt.)VMware, Inc. Stephen DiamondLawrence Lamers (Alt.)INCITS Technical Committee T10 on SCSI Storage Interfaces, which developed andreviewed this standard, had the following members:Ralph O. Weber, ChairWilliam Martin, Vice-ChairJohn Geldman, SecretaryOrganizatio

48、n Represented Name of RepresentativeAmphenol Corporation Gregory McSorleyBrad Brubaker (Alt.)David Chan (Alt.)Paul Coddington (Alt.)Michael Craton (Alt.)Zhineng Fan (Alt.)Adrian Green (Alt.)Donald Harper (Alt.)Martin Li (Alt.)Chris Lyon (Alt.)Alex Persaud (Alt.)Chansy Phommachanh (Alt.)Michael Schol

49、eno (Alt.)Dave Sideck (Alt.)Michael Wingard (Alt.)CN Wong (Alt.)Matt Wright (Alt.)Avago TechnologiesGeorge PenokiePatrick Bashford (Alt.)Brad Besmer (Alt.)Srikiran Dravida (Alt.)Rick Kutcipal (Alt.)Bernhard Laschinsky (Alt.)Harvey Newman (Alt.)Robert Sheffield (Alt.)James Smart (Alt.)Bill Voorhees (Alt.)Brocade.David PetersonScott Kipp (Alt.)Steven Wilson (Alt.)Dell, Inc. Kevin MarksMark Bokhan (Alt.)Gary Kotzur (Alt.)Bill Lynn (Alt.)Ash McCarty (Alt.)Daniel Oelke (Alt.)EMC Corporation David BlackErin Bourniv