ImageVerifierCode 换一换
格式:PDF , 页数:77 ,大小:358.17KB ,
资源ID:435661      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-435661.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(ANSI INCITS 365-2002 Information Technology - SCSI RDMA Protocol (SRP).pdf)为本站会员(unhappyhay135)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

ANSI INCITS 365-2002 Information Technology - SCSI RDMA Protocol (SRP).pdf

1、ANSI INCITS 365-2002for Information Technology SCSI RDMA Protocol (SRP)ANSIINCITS365-2002ANSIINCITS 365-2002American National Standardfor Information Technology SCSI RDMA Protocol (SRP)SecretariatInformation Technology Industry Council (ITI)Approved November 21, 2002American National Standards Insti

2、tute, Inc.AbstractThis standard describes the message format and protocol definitions required to transfer commands anddata between a SCSI (Small Computer System Interface) initiator port and a SCSI target port using anRDMA communication service.Approval of an American National Standard requires rev

3、iew 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 interes

4、ts. 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 do

5、es 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 g

6、ive 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 spon

7、sor 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. Purchas

8、ers 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 2002 by Information Tech

9、nology 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, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers

10、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 to this sta

11、ndard. 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 standard it pro

12、cesses. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.iContentsPageForeword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vIntroduction . . . . . . . . . . . . . . .

13、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14、. . . .22.1 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22.2 Approved references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22.3 References under development . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Defini

15、tions, symbols, abbreviations and conventions . . . . . . . . . . . . . . . . . . .33.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33.2 Acronyms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43.3 Ke

16、ywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43.4 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53.5 Notation for procedures and functions. . . . . . . . . . . . . . . . . . . . . . . .64 RDMA comm

17、unication service model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74.2 RDMA Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74.2.1 Intro

18、duction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74.2.2 Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84.2.3 Disestablishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19、104.3 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104.4 RDMA operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20、. . .104.4.2 RDMA Write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114.4.3 RDMA Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114.5 Ordering and Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21、. . . .114.5.1 Ordering and reliability overview . . . . . . . . . . . . . . . . . . . . . . . . . . .114.5.2 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114.5.3 Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22、. . . . . . . . .125 Structure and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135.1 Overview of SRP operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135.1.1 RDMA channel establishment and login . . . . . . . . . . . . . . . . . . .

23、 . .135.1.2 Single RDMA channel operation . . . . . . . . . . . . . . . . . . . . . . . . . . .135.1.3 Multiple independent RDMA channel operation . . . . . . . . . . . . . . .135.1.4 RDMA channel disconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145.2 Identifiers. . . . . . . .

24、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155.3 Alias associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155.4 Information unit classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155.5 SRP target port buffer

25、management . . . . . . . . . . . . . . . . . . . . . . . .155.5.1 Buffer management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155.5.2 SRP requests issued by target port. . . . . . . . . . . . . . . . . . . . . . . . .155.5.3 Requests issued by initiator port . . . . . . . . .

26、 . . . . . . . . . . . . . . . . . .155.6 Data buffers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175.6.1 Memory descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175.6.2 Data buffer descriptors . . . . . . . . . . . . . . .

27、. . . . . . . . . . . . . . . . . . .186 SRP Information Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236.1 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23iiPage7 SCSI mode parameters . . . . . . . . . .

28、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.1 SCSI mode parameter overview and codes . . . . . . . . . . . . . . . . . . 487.2 Disconnect-reconnect mode page . . . . . . . . . . . . . . . . . . . . . . . . . 487.2.1 Valid fields . . . . . . . . . . . . . . . . . . . . . . . . . .

29、 . . . . . . . . . . . . . . . . . 497.2.2 Invalid fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.3 Protocol specific LUN page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.4 Protocol specific port page . . . . . . . . . . . . . . . .

30、 . . . . . . . . . . . . . . . 49AnnexesA SRP interface protocol and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52B SRP for the InfiniBandTMArchitecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57iiiPageTables1 Memory descriptor . . . . . . . . . . . . . . .

31、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Data buffer descriptor formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Supported data buffer descriptor formats . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Indirect data buffer descriptor. .

32、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 SRP requests sent from SRP initiator ports to SRP target ports . . . . . . . . . 236 SRP responses sent from SRP target ports to SRP initiator ports . . . . . . . . 237 SRP requests sent from SRP target ports to SRP initiator p

33、orts . . . . . . . . . 238 SRP responses sent from SRP initiator ports to SRP target ports . . . . . . . . 239 SRP_LOGIN_REQ request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2510 MULTI-CHANNEL ACTION code values . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34、 . . . 2611 SRP_LOGIN_RSP response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2712 MULTI-CHANNEL RESULT code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2813 SRP_LOGIN_REJ response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35、. . . . 2914 SRP_LOGIN_REJ response reason codes . . . . . . . . . . . . . . . . . . . . . . . . . 3015 SRP_I_LOGOUT request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116 SRP_T_LOGOUT request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36、 . . 3217 SRP_T_LOGOUT request reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 3318 SRP_TSK_MGMT request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3419 TASK MANAGEMENT FUNCTION CODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

37、20 SRP_CMD request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3621 TASK ATTRIBUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3722 SRP_RSP response . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

38、 . . . . . . . . . . . . . . 3923 RESPONSE DATA field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4224 RSP_CODE values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4225 SRP_CRED_REQ request . . . . . . . . . . . .

39、 . . . . . . . . . . . . . . . . . . . . . . . . . . 4326 SRP_CRED_RSP response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4427 SRP_AER_REQ request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4528 SRP_AER_RSP response . . . . . . . . .

40、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4729 SRP mode page codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4830 Disconnect-reconnect mode page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48ivFigures1 SCSI document relations

41、hips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 RDMA communication service example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Example RDMA channel establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Memory descriptor mapping . . .

42、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Example indirect data buffer descriptor with no PARTIAL MEMORY DESCRIPTOR LIST field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Example indirect data buffer descriptor with a PARTIAL MEM

43、ORY DESCRIPTOR LIST field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22viForeword (This foreword is not part of ANSI INCITS 365-2002.)The purpose of this standard is to define a SCSI transport protocol based on RemoteDirect Memory Access (RDMA). This standard

44、was developed by INCITS technicalcommittee T10, which forwarded it to INCITS on a unanimous vote.With any technical document, there may arise questions of interpretation as newproducts are implemented. INCITS has established procedures to issue technicalopinions concerning the standards developed by

45、 INCITS. These procedures may re-sult in SCSI Technical Information Bulletins being published by INCITS. These Bulle-tins, while reflecting the opinion of the Technical Committee that developed thestandard, are intended solely as supplementary information to other users of thestandard. This standard

46、, ANSI INCITS 365-2002, as approved through the publica-tion and voting procedures of the American National Standards Institute, is not al-tered by these bulletins. Subsequent revisions to this standard may not reflect thecontents of these Technical Information Bulletins.Requests for interpretation,

47、 suggestions for improvement and addenda, or defect re-ports are welcome. They should be sent to the INCITS Secretariat, Information Tech-nology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922.This standard was processed and approved for submittal to ANSI by InterNational

48、Committee 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:Karen Higginbottom, ChairRuss Richards, Vice-ChairJennifer Gar

49、ner, SecretaryOrganization Represented Name of RepresentativeApple Computer, Inc. David MichaelWanda Cox (Alt.)Hewlett-Packard Company. Karen HigginbottomScott Jameson (Alt.)Steve Mills (Alt.)Hitachi America, Ltd. John NeumannHarukazu Miyamoto (Alt.)IBM Corporation . Ronald F. SillettiChuck Adams (Alt.)Institute for Certification of Computer Professionals. Kenneth M. ZemrowskiThomas Kurihara (Alt.)Intel Corporation. Gregory KisorMichelle Stamnes (Alt.)Philip Wennblom (Alt.)Microsoft Corporation Mike KsarJoseph Zajaczkowski (Alt.)Mike Deese (Alt.)National Institute of Standards equivalent

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1