最全最新的SAS 3 协议 SCSI - 3

【实例简介】
最新最全的 T10 的 SCSI Gen 3 协议，包括PHY，Physical，Link, Trans, 端口层，应用层， 及SATA兼容协议。 非常完整。 物理层可与我原先分享的SAS-3 做补充。 是完整的协议。 请勿传播。
04 February 2014 T10/BSR INCITS 492 Revision 06e American National standard for Information Technology SAS Protocol Layer-3(SPL-3) Secretariat Information Technology Industry Council Approved mm dd yy American National standards Institute. Inc ABSTRACT This standard specifies three transport protocols used over the SAs interconnect specified in SAS-3, one to transport scSI commands, another to transport serial ata commands to multiple sata devices, and a third to support interface management. This standard is intended to be used in conjunction with SAS standards SCSI command set standards, and ata command set standards Working Draft SAS Protocol Layer-3 (SPL-3 T10/ BSR INCITS 492 Revision 06e 04 February 2014 Ar merican Approval of an AI merican National standard requires verification by ansi that the requirements for due process, consensus, and other criteria for approval have been met by N ational the standards developer Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially Standard affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity Consensus requires that all views and objections be considered and that effort be made towards their resolution The use of american National Standards is completely voluntary their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards The American National standards institute does not develop standards and will in no circumstances give interpretation on any American National Standard Moreover, no person shall have the right or authority to issue an interpretation of an american National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National standards Institute CAUTION: The developers of this standard have requested that holders of patents that may be required 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 identify which patents, if any, may apply to this standard As of the date of publication of this standard, following calls for the identification of patents that may be required for the implementation of the standard, notice of one or more claims has been received By publication of this standard, no position is taken with respect to the validity of this claim or of any rights in connection therewith The known patent holder(s)has(have) however, filed a statement of willingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license Details may be obtained from the publisher No further patent search is conducted by the developer or the publisher in respect to standard it processes. No representation is made or implied that licenses are not any required to avoid infringement in the use of this standard Published by American National standards Institute E 42nd25 West 43rd Street 4th floor new york. new york 10036-7422 Copyright C 2014* by Information Technology Industry Council(ITI). All rights reserved No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise without prior written permission of iTl, 1101 K Street NW, Suite 610, Washington, DC 20005-7031 Printed in the united states of america Working Draft SAS Protocol Layer-3 (SPL-3) 04 February 2014 T10/BSR INCITS 492 Revision 06e Revision Information R1 Revision SPL-3 roo(12 November 2012 First release of SPL-3. The project proposal was 11-348rO Incorporated these a) Edits received from ANSI editing processing b) It was voted on in the phy working group meeting on 1/10/12 to remove G3 transmitter training(y-13, n-1, a-4). This was voted on in the protocol working group meeting on 1/9/12 to be removed (y-5, n-0 a6) As a result in section 5. 12. 4. 12. 1 ( State description) item 1)A)c)and item 1)B)b)should have been deleted and item 1)A)d) should have been changed to <<d) the highest priority commonly supported setting indicates G1, G2, or G3; >> and c)As a result of an email from Rob Elliott. on 7/11/2012 The task manager doesn't ever send INVALID FRAME; the ST TFR state machine, which is part of the SCsi target port, does that (see page 473, 496, 497). So, the Task Management Function Executed is never invoked with that value. Therefore, I think table 202 is mostly correct; it just needs upgrade a)to f) in e), change TASK MANAGEMENT FUNCTION FAILED: to"SERVICE DELIVERY OR TARGET FAILURE -Task Management Function Failed: "(until Joe writes a proposal to give that its own Service Response) Table 203 represents what is received by the scsI initiator port and mapped via Received TMF Executed o to the application client; this does need to handle INVALID FRAME, TASK MANAGEMENT FUNCTION FAILED. and OVERLAPPED INITIATOR PORT TRANSFER TAG ATTEMPTED(as it does) R2 Revision SPL-3 ro1(21 November 2012) Incorporated these a)12-303r1 NOTIFY(POWER LOSS EXPECTED) Clarification [ Voorhees] b)12-315r1 Fixes Resulting from SPL-2 Letter Ballot Comments [Penokie c)12-316r1 SMP Open Priority [Penokie d)12-347r1 CDB Length Error Fix [Penokie] e)12-419r1 Inside ZPSDS persistent=0 is broken [Penokie]; and f) 12-429r0 STP CONTINUE AWT bit description clarification [Symons] R3 Revision SPL-3 r02 (16 January 2013) Incorporated these a) 12-251r8 SPL-3 Persistent Connection [Penokie; and b) as a result of an email from Rakesh KN on 11/25/2012 it was discovered that an accepted letter ballot comment had not been completely implemented As a result in Figure 103-PTT SC1, PTT SC2 and Ptt sC3(phy layer transmitter training set transmitter coefficient) state machines the Set Coefficient 1 Request(Hold )message from PTT_R was not changed to Set Coefficient 1 Request (i.e the Hold argument should have been deleted). This change was made in the PTT SC1 0: ldle state description making the text inconsistent with the figure. The figure has been corrected in this revision of spl-3 R 4 Revision SPL-3 r03(09 May 2013) Incorporated these a)13-055r2 SPL-3: Fixes to persistent connection [Penokie Working Draft SAS Protocol Layer-3 (SPL-3) T10/ BSR INCITS 492 Revision 06e 04 February 2014 b)12-401r5 Add reporting of PoWER DISABLE signal support [Houlder c)13-006r2 Clarifications to SP_PC and sP_P s State Machines [Penokie d)13-116r1 Resolve inconsistency in SMP PHY EVENTS [Besmer e)13-117r1 Clarify Notation for procedure calls [Weber f13-120r0 Retain MAXIMUM BURST SIZE field in the Disconnect-Reconnect mode page [symons ] and g) As a result of an email from Joe Breher on 4/15/2013 that stated: I ran across something that seems confusing to me. Is there a difference between a sas logical Phy and a logical sas Phy? the incorrect term "Logical SAs Phy" was changed to SAS Logical Phy. While looking into this it was discovered that the term "Logical Expander Phy was also incorrect and was changed to " Expander Logical Phy "This terms were incorrect tabled in the original proposal (07-094)that defined the UML section where both improper terms where first used R5 Revision SPL-3 ro4 (24 July 2013) Incorporated these a) 12-380rg SPL-3: Management ECM/ Application Client connection close request [Penokie] b)13-158r3 SPL-3: Fixes [Penokie c)13-182r1 SPL-3: CRC Clarifications [Voorhees] d) Completed the conversion of the glossary to ISO style e)As a result of an email from Bill Voorhees on 6/25/2013 that stated: There has been some confusion on what the references from Pl oc to section 4.1.13 are really pointing to The suggested clarification involves splitting section 4.1.13 into two subsections, the first describing how persistent connections behave and the second describing how support is defined, as given by the VPD mode page and Discover response. Then section 4.1.13.2 can be specifically referenced in the various portions of PL oc discussing supported/not supported persistent connection cases. The requested change was made f) Changed the".shall be set to the value defined in table XX. to"...shall be set as shown in table XXx for the <stable title>>. " throughout the standard to match the current convention for defining table cells that contain a fixed value R6 Revision SPL-3 r05 (25 September 2013) Incorporated these a)13-206r2 Missing Obsolete notation and other issues from 09-374 [Penokie ]; b) 13-208r1 Would Hunt [penokie c)13-216rO Last set of fixes before LB [Penokie )13-222r1 Persistent Connection Establishment Fix [Penokie] e) As a result of an email from rob elliott on 8/27/2013 that stated "It appears that spl- ro5 did not fully incorporated 09-374r3 (" Miscellaneous Fixes"by you) issue 1. The missing text from proposal 09-374r3 was added to table 271 f) As the result of an iSo request Gbps was changed to Gbit/s g)As a result of an email from Pooja Gupta on 9/11/2013 the incorrect mTT timer was changed to MRTT in figure 79 and figure 80 and fixed some of the colors in figure 80 R7 Revision SPL-3 ro6(25 September 2013) Cleared all change bars and markups from the previous revision Working Draft SAS Protocol Layer-3(SPL-3) 04 February 2014 T10/BSR INCITS 492 Revision 06e Contents Pa Revision Information 面面国国面画 Foreword (This foreword is not part of this standard) XXXVII Introduction 1 Scope 2 Normative references 2.1 Normative references 2.2 Approved references 2.3 References under development 2. 4 other references 1B面 3 Definitions, symbols, abbreviations, keywords, and conventions 333455 3.1 Definitions 3.2 Symbols and abbreviations 3.2.1 Abbreviations 27 3.2.2 Units 30 3.2.3 Symbols 30 3.2.4 Mathematical operators 30 3.3 Keywords 31 3, 4 Editorial conventions 32 3.5 Numeric and character conventions 33 3.5. 1 Numeric conventions 33 3.5.2 Units of measure 34 3.5.3 Byte encoded character strings conventions .34 3.6 UML notation conventions .35 3. 6. 1 Notation conventions overview 35 3.6.2 Constraint and note conventions 35 3.6.3 Class diagram conventions .36 3.6.4 Object diagram conventions 40 3.7 State machine conventions 42 3.7. 1 State machine conventions overview 42 3.7.2 Transitions∴ 43 3.7.3 Messages, requests, indications, confirmations, responses, and event notifications 43 3.7 4 State machine counters timers and variables 43 3.7.5 State machine arguments…… 44 38 Bit and byte ordering… 44 3. 9 Notation for procedures and functions 45 4 General 46 4.1 Architecture∴ 46 4.1.1 Architecture overview 46 4.12 Physical links and phys……… 48 4.1.3 Logical links 52 4.1.4 Narrow ports and wide ports…… .52 4.1.5 Application clients and device servers 56 4.1.6 sAS devices .56 4.1.7 Expander devices 4.1.8 Service delivery subsystem 58 4.1.9 Domains 1, .59 4.1.10 Expander device topologies 62 4.1.10. 1 Expander device topology overview 62 4.1.10.2 Expander device topologies 63 4.1.11 Pathways 65 4.1.12 Connections 65 Working Draft SAS Protocol Layer-3 (SPL-3) T10/ BSR INCITS 492 Revision 06e 04 February 2014 4.1.13 Persistent connections 67 4.1.13.1 Persistent connection operation 67 4.1.13.2 Persistent connection support 68 4.1.14 Advancing credit 68 41.15 Broadcasts 68 42 Names and identifiers 70 4.2.1 Names and identifiers overview 70 4.2.2 NAA IEEE Registered format identifier 72 4.2. 3 NAA Locally assigned format identifier 4.2, 4 SAS address 73 4.2.5 Hashed sas addresses 73 4.2.6 Device names and expander device SAS addresses 74 4.2.7 Device names for sata devices with world wide names 4.2.8 Port names 75 4.2. 9 Port identifiers and sas port sas addresses 75 4.2. 10 Phy identifiers 76 4.3 State machines… …………77 43. 1 State machine overyiew 77 4.3.2 Transmit data path 78 4.3.3 Receive data path 83 4.3.4 State machines and SAS Device, SAS Port, and Sas Phy classes .87 4. 4 Events 89 4.4.1 Reset sequences 89 4.4.2 Hard reset 4.4.2.1 Hard reset overview 面 91 4.4.2.2 Additional hard reset processing by SAS ports 91 4. 2. 3 Additional hard reset processing by expander ports 9 44.3 T nexus loss 4.4.4 Power loss expected 92 4.5 Expander device model .::::: 93 4.5. 1 Expander device model overview 面面国1面1面面 93 4.5.2 EXpander ports 94 4.5.3 Expander connection manager(ECM).………… 95 4.5. 4 Expander connection router(ECR) 95 4.5.5 Broadcast propagation processor(BPP) 96 4.5.6 Expander device interfaces 96 4.5.6. 1 Expander device interface overview 96 4.5.6.2 Expander device interfaces detail 98 45.6.3 ECM interface 99 4.5.6. 4 ECR interface 101 4.5. 6.5 BPP interface 103 4.5.7 Expander device routing 104 4.5.7.1 Routing attributes and routing methods 104 4.5.7. 2 Expander device topology routing attribute restrictions 105 4.5.7.3 Connection request routing 105 4.5.7 4 Expander route table 105 4.5.7. 4.1 Expander route table overview 105 4.5.7.4.2 Phy-based expander route table 106 4.5.7.4.3 Expander-based expander route table 107 4.5.8 Expander device reduced functionality 107 4.5.9 Broadcast(Expander) handling .108 4.6 Discover process 108 4.6.1 Discover process overview……...…… 108 4.6.2 Starting the discover process( Broadcast( Change) handling).,……………………,108 4.6. 3 Discover process traversal 109 4.6. 4 Discover process in a self-configuring expander device 4.6.5 Enabling multiplexing 112 Working Draft SAS Protocol Layer-3 (SPL-3) 04 February 2014 T10/BSR INCITS 492 Revision 06e 4.7 Configuration subprocess 112 4.7.1 Configuration subprocess overview…… 12 4.7.2 Allowed expander device topologies 113 4.7. 3 Externally configurable expander device route table optimization 114 4.7.4 Externally configurable expander device expander route index order .115 4.8 Zoni 122 4.8.1 Zoning overview .122 4.8.2 Zoning expander device requirements ∴126 4.8.3 Zoning operation 129 4.8.3. 1 Zone phy information. 129 4.8.3.2 Zone groups 132 4.8.3.3 Zone permission table 132 4.8.3.4 Zoning expander route table…… 134 4.8. 3.5 Source zone group and destination zone group determination 135 4.8. 4 Zone phy information and link reset sequences 136 4.8.5 Broadcast processing in a zoning expander device with zoning enabled 139 4.8.6 Zone configuration……… …140 4.8.6. 1 Zone configuration overview 140 4.8.6.2 Lock step 140 4.8.6.3 Load step………… 141 4.8.6. 4 Activate step 142 4.8.6.5 Unlock step 142 4.8.6.6 Zone lock inactivity timer .143 4.8.6. 7 Enable a zoning expander device 143 4.9 Sas device and expander device power conditions 143 4. 10 Phy power conditions .144 4.10.1 Low phy power conditions 1,画面B画面1面1 144 4.10.1. 1 Low phy power conditions overview ..144 4. 10.1.2 Active phy power condition 144 4. 10.1.3 Partial phy power condition 144 4.10.1. 4 Slumber phy power condition 面面B国国国面画 144 4. 10.1.5 End device low phy power conditions 145 4. 10.1.6 Expander device low phy power conditions 国面 145 4.10.2 SATA phy power conditions 146 4. 1 1 Phy test functions 146 4.11. 1 Phy test functions overview 146 4.11.2 Transmit pattern phy test function …147 4.12 Phy events… .147 4. 13 Using POWER DISABLE signal to create a power on event 152 4.13. 1 Using POWER DISABLE signal to create a power on event overview 152 4.13.2 Discovering POWER DISABLE signal support 152 4.13. 3 Using a management device server to control the PoWER DISABle signal 153 5 Phy layer 154 5. 1 Phy la 154 5.28b10 b coding.….……… .154 5.2. 1 8b 10b coding overview 154 5.2.2 8b10b coding notation conventions .154 5. 3 Character encoding and decoding 155 5.3. 1 Introduction 155 5.3.2 Bit transmission order 155 5.3.3 Character transmission order 155 5.3.4 Frame transmission order 156 5.3.5 Running disparity(RD) 156 5.3.6 Data characters 画1E 156 5.3.7 Control characters ∴162 5.3.8 Encoding characters in the transmitter .163 Working Draft SAS Protocol Layer-3 (SPL-3 T10/ BSR INCITS 492 Revision 06e 04 February 2014 5.3.9 Decoding characters in the receiver 163 5. 4 Dwords, primitives, data dwords, and invalid dwords …164 5.5 Bit order 164 5.6 Out of band (ooB)signals ….….166 5.6. 1 OOB signals overview..... 166 5.6.2 Transmission of oob signals 166 5.6.3 Receiver detection of ooB signals 167 5.6. 4 SATA port selection signal 169 5.6.5 Phy power conditions 170 5.7 Phy capabilities bits……… 170 5. 8 BMC coding 174 5.8. 1 BMC coding overview 174 5.8.2 TTIU bit cell encoding in the transmitter……… 175 5.8.3 ttiu bit transmission order 176 5.8.4 TTIU bit cell decoding in the receiver 176 5.9 Train TX-SNW TTIUS 177 5.9.1 Train Tx-SnW TtIU format 1B面面面日1国L面 177 5.9.2 Control/status ttiu 178 5.9.3 Error Response TTiU 182 5. 10 Phy reset sequences ∴184 5.10.1 Phy reset sequences overview .184 5.10.2 SATA phy reset sequence 185 5.10.2.1 SATA OOB sequence…… 185 51022 SATA speed negotiation sequence…………………… 186 5. 10.3 SAS to SATa phy reset sequence 186 5. 10.4 SAs to SAS phy reset sequence 188 5. 10.4.1 SAS OOB sequence 188 5.10.4.2 SAs speed negotiation sequence 191 5.10.4.2.1 SAS speed negotiation sequence overview 191 5.10.4.2.2 SAS speed negotiation sequence timing specifications 192 5.10.4.2.3 Speed negotiation window(SNW)definitions 193 5.10.4.23. 1 snW definitions overview 193 5.10.423.2 SNW-1. SNW-2, and Fina -SNW 194 5.10.4.23.3SNW-3 195 5.10. 4.2. 3 4 Train Tx-SNW ..: 197 5.10.4.2.3.4. 1 Phy's transmitter initial condition 197 5.10.4.23.42 Transmitter training…… 197 5.104.2.3.4.3 Pattern marker.…… .198 5. 10.42.3.5 Train Rx-SNW 200 5.10.4.2. 4 SAS speed negotiation sequence 203 5.10.4.2.5 SAS speed negotiation sequence examples 1B面 204 5.10.4.2.6 Train Tx pattern sequence 5. 10.4.2.6. 1 Train Tx pattern sequence overview 212 5.10.4.2.6.2 Train Tx pattern initial sequence 213 5.10.4.2.6.3 Train Tx pattern handshake sequence. 216 5.10.4.2.6.3.1 Train_ Tx pattern handshake sequence overview…….…..… 216 5.10.4.2.6.3.2 Attached phy's receiver increment or decrement request 216 5. 10.4.2.6.3. 3 Attached phy's receiver reference 1, reference 2, or no equalization request.. 219 5. 10.4.2.6. 4 Train Tx pattern completion sequence 221 5.10.4.2.6.5 Invalid tt| U sequence…… 224 5. 10.4.3 Multiplexing sequence ∴225 5. 10.5 Phy reset sequence after devices are attached 226 5. 11 Phy power condition sequences 227 5. 11. 1 Transitioning from the active phy power condition to a low phy power condition .227 5. 11.2 Transitioning from a low phy power condition to the active phy power condition 228 5.11.3 Events during low phy power condition 228 5. 12 SP(phy layer) state machine 230 Working Draft SAS Protocol Layer-3(SPL-3) 【实例截图】
【核心代码】