《ANSI-INCITS-337-2000.pdf》由会员分享，可在线阅读，更多相关《ANSI-INCITS-337-2000.pdf（110页珍藏版）》请在三一文库上搜索。
1、ANSI INCITS 337-2000 (formerly ANSI NCITS 337-2000) for Information Technology Scheduled Transfer Protocol (ST) Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57 MDTNo r
2、eproduction or networking permitted without license from IHS -,-,- Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57 MDTNo reproduction or networking permitted without l
3、icense from IHS -,-,- ANSI NCITS 337-2000 American National Standard for Information Technology Scheduled Transfer Protocol (ST) Secretariat Information Technology Industry Council (ITI) Approved August 24, 2000 American National Standards Institute, Inc. Abstract This standard specifies a connectio
4、n-oriented data transfer protocol supporting flow-controlled Read and Write sequences and non-flow-controlled, persistent-memory Put, Get and FetchOp sequences. For all sequences, small control messages are used to pre-allocate buffers at the data Destination before the data movement begins, thus al
5、lowing the data to be moved immediately from the physical network into the end devices memory. The control and data messages may use different physical media or may share a single physical medium. Procedures are provided for moving data over HIPPI and other media. Copyright American National Standar
6、ds Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57 MDTNo reproduction or networking permitted without license from IHS -,-,- American National Standard Published by American National Standards Institute, I
7、nc. 11 West 42nd Street, New York, NY 10036 Copyright 2000 by Information Technology Industry Council 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 the publisher. Printed in the Unit
8、ed States of America Approval of an American National Standard requires review by ANSI that the require- ments for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgement of the ANSI Board of Standards Re- view
9、, substantial agreement has been reached by directly and materially affected in- terests. Substantial agreement means much more than a simple majority, but not nec- essarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their r
10、esolution. 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 proce- dures not conforming to the standards.
11、The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American Na- tional Standard in the name of the American
12、National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name ap- pears 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 Stand
13、ards 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 call- ing or writing the American National Standards Institute. CAUTION: The developers of this stand
14、ard 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, if any, patents may apply to this standard. As
15、of the date of publication of this standard and following calls for the identification of patents that may be required for the implementation of the standard, no such claims have been made. No further patent search is conducted by the developer or publisher in respect to any standard it processes. N
16、o representation is made or implied that li- censes are not required to avoid infringement in the use of this standard. Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57
17、 MDTNo reproduction or networking permitted without license from IHS -,-,- i Contents Page Foreword vi Introduction.x 1 Scope1 2 Normative references.1 3 Definitions and conventions2 3.1 Definitions2 3.2 Editorial conventions4 3.2.1 Binary notation4 3.2.2 Hexadecimal notation.4 3.3 Acronyms and othe
18、r abbreviations4 4 System overview.5 4.1 Control Channels, Control operations, Data Channels, and Data operations .5 4.2 Virtual Connections6 4.3 Data hierarchy .6 4.4 Scheduled Transfers .6 4.5 Persistent memory region6 4.6 Destination side data structure model.6 4.7 Implementing subsets of ST capa
19、bilities.8 5 Connection management .9 5.1 Connection management sequences9 5.1.1 Virtual Connection setup.9 5.1.2 Virtual Connection teardown.10 5.2 Connection management parameters.11 5.2.1 Ports .11 5.2.2 Keys11 5.2.3 ST Buffer Size and Bufsize.12 5.2.4 Max_STU size 12 5.2.5 Slots12 5.2.6 EtherTyp
20、e.13 6 Data movement13 6.1 Data movement sequences.13 6.1.1 Common sequences.13 6.1.1.1 Nop14 6.1.1.2 Request Slot state .14 6.1.1.3 Request Transfer state14 6.1.1.4 Request Block state.15 6.1.1.5 End sequence16 6.1.2 Write sequence.16 6.1.3 Read sequence.19 6.1.4 Persistent memory sequences.21 6.1.
21、4.1 Allocate a persistent memory region .22 6.1.4.2 Put sequences.23 6.1.4.3 Get sequences 24 6.1.4.4 FetchOp sequences 25 6.2 Data movement parameters26 6.2.1 Sequence identifiers (I-id, R-id)26 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Emp
22、loyees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57 MDTNo reproduction or networking permitted without license from IHS -,-,- ii Page 6.2.2 Blocks.27 6.2.3 Block numbers (B_num, F_num, G_num)27 6.2.4 Block numbers in state responses (B_num, B_seq) 28 6.2.5 Maximum Block size
23、 (Max_Block)28 6.2.6 Block size28 6.2.6.1 Consistent Block sizes (2Blocksize) .29 6.2.6.2 Variable Block sizes (V-BlkSize)29 6.2.7 Blocks enabled (CTS_req) .29 6.2.8 STUs and STU_num 30 6.2.9 Bufx.30 6.2.10 Offset30 6.2.10.1 Buffer-referenced (Offset, F-Offset) 30 6.2.10.2 Transfer-referenced (V-Byt
24、eSeq) 31 6.2.11 Transfer length (T_len).31 6.2.12 Sync31 6.2.13 Memory Index (Mx).31 6.2.14 Opaque data.32 6.2.15 Block window (B_winreq, B_win)32 6.3 Tiling examples32 7 Operations management35 7.1 Flow control .35 7.2 Status operations.35 7.3 Rejected operations.35 7.4 Interrupts35 8 Schedule Head
25、er35 8.1 Op codes .36 8.2 Flags36 8.3 Checksum (optional)37 8.3.1 Checksum algorithm.37 8.3.2 Transmitting checksums.38 8.3.3 Receiving checksums.38 8.3.4 Data checksum example38 9 Operations sequence tables.39 10 Error processing .43 10.1 Operation timeout43 10.2 Operation pairs43 10.3 Data transmi
26、ssion timeouts.43 10.4 Keep-alive sequences (optional) .44 10.5 Duplicated operations44 10.5.1 Duplicate Request_Connection45 10.5.2 Duplicate Connection_Answer45 10.5.3 Duplicate Request_Disconnect.45 10.5.4 Duplicate Disconnect_Answer45 10.5.5 Duplicate End .46 10.5.6 Duplicate Request_State46 10.
27、5.7 Duplicate Request_To_Send46 10.5.8 Duplicate Request_To_Receive.46 10.5.9 Duplicate Clear_To_Send.46 10.5.10 Duplicate Request_Memory_Region46 Copyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for
28、Resale, 04/29/2007 13:23:57 MDTNo reproduction or networking permitted without license from IHS -,-,- iii Page 10.5.11 Duplicate Get47 10.5.12 Duplicate FetchOp47 10.5.13 Duplicate Data for a FetchOp.47 10.5.14 Other duplicate operations48 10.6 Checksum errors.48 10.7 LLP error48 10.8 Syntax errors
29、.48 10.8.1 Undefined Opcode48 10.8.2 Unexpected Opcode.48 10.9 Virtual Connection errors.48 10.9.1 Invalid Key or Port.48 10.9.2 Slots exceeded.48 10.9.3 Unknown EtherType.48 10.9.4 Illegal Bufsize49 10.9.5 Illegal STU size.49 10.10 Scheduled Transfer errors.49 10.10.1 Invalid sequence identifier49
30、10.10.2 Invalid Memory Index (Mx) .49 10.10.3 Bad Data Channel specification49 10.10.4 Out of Range B_num, Bufx, Offset, or STU_num 49 10.10.5 Block out of order error.49 10.10.6 Missing or flawed Block recovery.49 10.10.7 Illegal Blocksize50 10.10.8 Undefined Flag .50 10.10.9 Unsupported sequence e
31、rror50 Tables 1 Response to a rejected operation35 2 Op codes and operations.36 3 Connection management sequences40 4 Common control sequences40 5 Write sequences41 6 Read sequences41 7 Put, Get, and FetchOp sequences 42 8 Operation pairs guarded by Op_timeout with retry43 9 Summary of logged errors
32、.50 B.1 Defined option-codes.58 D.1 Transfer example operations.69 D.2 Anti-aliasing tools summary.76 E.1 State table syntax 77 E.2 Connection setup example80 E.3 Connection teardown example80 E.4 Write sequence example.83 E.5 Persistent memory region setup example .86 E.6 Persistent memory region t
33、eardown example .86 E.7 Put sequence example88 E.8 Get sequence example88 E.9 FetchOp sequence example89 E.10 Connection management FSM90 E.11 Write sequence (Initiator side) FSM91 E.12 Write sequence (Responder side) FSM 92 E.13 Persistent memory region (Initiator side) FSM 93 Copyright American Na
34、tional Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57 MDTNo reproduction or networking permitted without license from IHS -,-,- iv Page E.14 Persistent memory region (Responder side) FSM.94 E.15
35、 Acknowledged Put sequence (Initiator side) FSM.95 E.16 Get sequence (Initiator side) FSM.95 E.17 FetchOp sequence (Initiator side) FSM.96 E.18 FetchOp sequence (Responder side) FSM.96 Figures 1 System overview5 2 Transmission units.5 3 User data hierarchy6 4 A Destination side data structure model7
36、 5 Connection management example9 6 Common sequence examples.13 7 Write example17 8 Read example19 9 Put, Get, and FetchOp examples 22 10 Consistent Block size data tiling example34 11 Schedule Header contents.35 12 Flags summary36 13 Data checksum example .39 A.1 An ST operation carried in a HIPPI-
37、6400-PH Message.52 A.2 An ST operation carried in a HIPPI-FP packet53 A.3 An ST operation carried in an IEEE 802.3 Ethernet packet.55 A.4 An ST operation carried in a DIX Ethernet packet.56 B.1 Option formats.58 C.1 ST striping configurations 61 D.1 Maximum STU size determination.63 D.2 Maximum Bloc
38、k size determination and pacing Clear_To_Send operations65 D.3 Example of a data Destinations Validation Table lookup67 D.4 Ks buffer layout .68 Annexes A Using lower layer protocols .51 A.1 HIPPI-6400-PH as the LLP .51 A.2 HIPPI-FP as the LLP.52 A.3 Ethernet as the LLP.54 A.4 ATM LAN Emulation as t
39、he LLP57 B Option payload format58 B.1 Option formats.58 B.2 Option-codes.58 B.2.1 End of list58 B.2.2 No_operation58 B.2.3 Linear address base.58 B.2.4 ULP parameter.59 B.2.5 ASCII error string59 B.2.6 Two-byte error code .59 B.2.7 V-BlkSize and V-ByteSeq.59 B.2.8 Experimental 59 C ST striping60 Co
40、pyright American National Standards Institute Provided by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57 MDTNo reproduction or networking permitted without license from IHS -,-,- v Page C.1 Striping principles60 C.2 Many-to-on
41、e striping .60 C.3 One-to-many striping.60 C.4 Many-to-many striping.61 D Implementation comments.62 D.1 Parameters expressed as 2n.62 D.2 Using Max_STU and Bufsize to determine the maximum STU size.62 D.3 Using Max_Block, Blocksize, and pacing Clear_To_Send operations .64 D.4 Implementing Bufx look
42、ups.66 D.5 Transfer example68 D.5.1 End device assumptions68 D.5.2 Interconnection assumptions.68 D.5.3 Notes for table D.1.70 D.5.4 Parameter notes 70 D.6 FetchOp buffer management72 D.7 V-BlkSize and V-ByteSeq comments73 D.8 Put Block window comments74 D.9 Aliased operations.75 E State tables 77 E
43、.1 Introduction77 E.1.1 Table syntax.77 E.1.2 Conventions in FSMs.78 E.2 General implementation issues.78 E.3 Connection management FSM .79 E.3.1 FSM interface to ULP assumptions79 E.3.2 Implementation Issues.79 E.3.3 Connection management examples 80 E.3.4 Connection management error examples81 E.4
44、 Write sequence FSMs.82 E.4.1 Assumptions.82 E.4.2 Implementation issues .82 E.4.3 FSM interface to ULP assumptions82 E.4.4 Write sequence example .83 E.4.5 Write sequence error examples.84 E.5 Read sequence FSMs.84 E.6 Persistent memory region FSMs.85 E.6.1 Assumptions.85 E.6.2 Implementation issue
45、s .85 E.6.3 FSM interface to ULP assumptions85 E.6.4 Persistent memory region examples85 E.6.5 Persistent memory region error examples.87 E.7 Put, Get, and FetchOp examples87 E.7.1 Put example .87 E.7.2 Get example.88 E.7.3 FetchOp example.89 Copyright American National Standards Institute Provided
46、by IHS under license with ANSI Licensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/29/2007 13:23:57 MDTNo reproduction or networking permitted without license from IHS -,-,- vi Foreword (This foreword is not part of American National Standard ANSI NCITS 337-2000.) This Americ
47、an National Standard specifies a connection-oriented data transfer pro- tocol supporting flow-controlled Read and Write sequences and non-flow-controlled, persistent-memory Put, Get and FetchOp sequences. For all sequences, small con- trol messages are used to pre-allocate buffers at the data Destin
48、ation before the data movement begins, thus allowing the data to be moved immediately from the physical network into the end devices memory. The control and data messages may use different physical media or may share a single physical medium. Proce- dures are provided for moving data over HIPPI and other media. This document includes annexes which are informative and are not considered part of the standard. Requests for interpretation, suggestions for improvement or addenda, or defect re- ports are w