draft-ietf-nfsv4-nfs-rdma-problem-statement-00.txt   draft-ietf-nfsv4-nfs-rdma-problem-statement-01.txt 
Internet-Draft Tom Talpey INTERNET-DRAFT Tom Talpey
Expires: August 2004 Network Appliance, Inc. Expires: January 2005 Network Appliance, Inc.
Chet Juszczak Chet Juszczak
Sun Microsystems, Inc. Sun Microsystems, Inc.
February, 2004 July, 2004
NFS RDMA Problem Statement NFS RDMA Problem Statement
draft-ietf-nfsv4-nfs-rdma-problem-statement-00.txt draft-ietf-nfsv4-nfs-rdma-problem-statement-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, I certify that any applicable
of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt The list of
Internet-Draft Shadow Directories can be accessed at
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This draft addresses applying Remote Direct Memory Access to the This draft addresses applying Remote Direct Memory Access to the
NFS protocols. NFS implementations historically incur significant NFS protocols. NFS implementations historically incur significant
overhead due to data copies on end-host systems, as well as other overhead due to data copies on end-host systems, as well as other
sources. The potential benefits of RDMA to these implementations sources. The potential benefits of RDMA to these implementations
are explored, and the reasons why RDMA is especially well-suited to are explored, and the reasons why RDMA is especially well-suited to
NFS and network file protocols in general are evaluated. NFS and network file protocols in general are evaluated.
Table Of Contents Table Of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2. Problem Statement . . . . . . . . . . . . . . . . . . . . 4 2. Problem Statement . . . . . . . . . . . . . . . . . . . . 5
3. File Protocol Architecture . . . . . . . . . . . . . . . . 5 3. File Protocol Architecture . . . . . . . . . . . . . . . . 6
4. Sources of Overhead . . . . . . . . . . . . . . . . . . . 7 4. Sources of Overhead . . . . . . . . . . . . . . . . . . . 8
4.1. Savings from TOE . . . . . . . . . . . . . . . . . . . . 8 4.1. Savings from TOE . . . . . . . . . . . . . . . . . . . . 9
4.2. Savings from RDMA . . . . . . . . . . . . . . . . . . . 9 4.2. Savings from RDMA . . . . . . . . . . . . . . . . . . . 9
5. Application of RDMA to NFS . . . . . . . . . . . . . . . . 10 5. Application of RDMA to NFS . . . . . . . . . . . . . . . . 10
6. Improved Semantics . . . . . . . . . . . . . . . . . . . . 10 6. Improved Semantics . . . . . . . . . . . . . . . . . . . . 11
7. Conclusions . . . . . . . . . . . . . . . . . . . . . . . 11 7. Conclusions . . . . . . . . . . . . . . . . . . . . . . . 11
Acknowledgements . . . . . . . . . . . . . . . . . . . . . 11 Acknowledgements . . . . . . . . . . . . . . . . . . . . . 12
References . . . . . . . . . . . . . . . . . . . . . . . . 12 Normative References . . . . . . . . . . . . . . . . . . . 12
Informative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 14
Full Copyright Statement . . . . . . . . . . . . . . . . . 15 Full Copyright Statement . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
The Network File System (NFS) protocol (as described in [RFC1094], The Network File System (NFS) protocol (as described in [RFC1094],
[RFC1813], and [RFC3530]) is one of several remote file access [RFC1813], and [RFC3530]) is one of several remote file access
protocols used in the class of processing architecture sometimes protocols used in the class of processing architecture sometimes
called Network Attached Storage (NAS). called Network Attached Storage (NAS).
skipping to change at page 12, line 10 skipping to change at page 12, line 22
protocol framework. A cautious evolutionary improvement of protocol framework. A cautious evolutionary improvement of
performance and semantics allows building on the value already performance and semantics allows building on the value already
present in the NFS protocol, while addressing new requirements that present in the NFS protocol, while addressing new requirements that
have arisen from the application of networking technology. have arisen from the application of networking technology.
8. Acknowledgements 8. Acknowledgements
The authors wish to thank Jeff Chase who provided many useful The authors wish to thank Jeff Chase who provided many useful
suggestions. suggestions.
9. References 9. Normative References
[RFC3530]
S. Shepler, et. al., "NFS Version 4 Protocol", Standards Track
RFC
[RFC1831]
R. Srinivasan, "RPC: Remote Procedure Call Protocol
Specification Version 2", Standards Track RFC
[RFC1832]
R. Srinivasan, "XDR: External Data Representation Standard",
Standards Track RFC
[RFC1813]
B. Callaghan, B. Pawlowski, P. Staubach, "NFS Version 3
Protocol Specification", Informational RFC
10. Informative References
[BRU99] [BRU99]
J. Brustoloni, "Interoperation of copy avoidance in network J. Brustoloni, "Interoperation of copy avoidance in network
and file I/O", in Proc. INFOCOM '99, pages 534-542, New York, and file I/O", in Proc. INFOCOM '99, pages 534-542, New York,
NY, Mar. 1999., IEEE. Also available from NY, Mar. 1999., IEEE. Also available from
http://www.cs.pitt.edu/~jcb/publs.html http://www.cs.pitt.edu/~jcb/publs.html
[CAL+03] [CAL+03]
B. Callaghan, T. Lingutla-Raj, A. Chiu, P. Staubach, O. Asad, B. Callaghan, T. Lingutla-Raj, A. Chiu, P. Staubach, O. Asad,
"NFS over RDMA", in Proceedings of ACM SIGCOMM Summer 2003 "NFS over RDMA", in Proceedings of ACM SIGCOMM Summer 2003
skipping to change at page 13, line 34 skipping to change at page 14, line 18
and Performance of the Direct Access File System (DAFS)", in and Performance of the Direct Access File System (DAFS)", in
Proceedings of 2002 USENIX Annual Technical Conference, Proceedings of 2002 USENIX Annual Technical Conference,
Monterey, CA, June 9-14, 2002. Monterey, CA, June 9-14, 2002.
[MOG03] [MOG03]
J. Mogul, "TCP offload is a dumb idea whose time has come", J. Mogul, "TCP offload is a dumb idea whose time has come",
9th Workshop on Hot Topics in Operating Systems (HotOS IX), 9th Workshop on Hot Topics in Operating Systems (HotOS IX),
Lihue, HI, May 2003. USENIX. Lihue, HI, May 2003. USENIX.
[NFSRDMA] [NFSRDMA]
T. Talpey, S. Shepler, "NFSv4 RDMA and Session Extensions", T. Talpey, S. Shepler, "NFSv4 Session Extensions", Internet
Internet Draft Work in Progress, draft-talpey-nfsv4-rdma- Draft Work in Progress, draft-ietf-nfsv4-session-00, February
sess-01, February 2004. 2004.
[PAI+00] [PAI+00]
V. S. Pai, P. Druschel, W. Zwaenepoel, "IO-Lite: a unified I/O V. S. Pai, P. Druschel, W. Zwaenepoel, "IO-Lite: a unified I/O
buffering and caching system", ACM Trans. Computer Systems, buffering and caching system", ACM Trans. Computer Systems,
18(1):37-66, Feb. 2000. 18(1):37-66, Feb. 2000.
[RFC3530]
S. Shepler, et. al., "NFS Version 4 Protocol", Standards Track
RFC
[RDDPPS] [RDDPPS]
Remote Direct Data Placement Working Group Problem Statement, Remote Direct Data Placement Working Group Problem Statement,
A. Romanow, J. Mogul, T. Talpey, S. Bailey, draft-ietf-rddp- A. Romanow, J. Mogul, T. Talpey, S. Bailey, draft-ietf-rddp-
problem-statement-03 problem-statement-04
[RFC1831]
R. Srinivasan, "RPC: Remote Procedure Call Protocol
Specification Version 2", Standards Track RFC
[RFC1832]
R. Srinivasan, "XDR: External Data Representation Standard",
Standards Track RFC
[RFC1813]
B. Callaghan, B. Pawlowski, P. Staubach, "NFS Version 3
Protocol Specification", Informational RFC
[RPCRDMA] [RPCRDMA]
B. Callaghan, T. Talpey, "RDMA Transport for ONC RPC", B. Callaghan, T. Talpey, "RDMA Transport for ONC RPC",
[SHI+03] [SHI+03]
P. Shivam, J. Chase, "On the Elusive Benefits of Protocol P. Shivam, J. Chase, "On the Elusive Benefits of Protocol
Offload", to be published in Proceedings of ACM SIGCOMM Summer Offload", to be published in Proceedings of ACM SIGCOMM Summer
2003 NICELI Workshop, also available from 2003 NICELI Workshop, also available from
http://issg.cs.duke.edu/publications/niceli03.pdf http://issg.cs.duke.edu/publications/niceli03.pdf
[SKE+01] [SKE+01]
skipping to change at page 14, line 43 skipping to change at page 15, line 17
Tom Talpey Tom Talpey
Network Appliance, Inc. Network Appliance, Inc.
375 Totten Pond Road 375 Totten Pond Road
Waltham, MA 02451 USA Waltham, MA 02451 USA
Phone: +1 781 768 5329 Phone: +1 781 768 5329
EMail: thomas.talpey@netapp.com EMail: thomas.talpey@netapp.com
Chet Juszczak Chet Juszczak
Sun Microsystems, Inc. Sun Microsystems, Inc.
43 Nagog Park 1718 Southwod Drive
Acton, MA 01720 USA Nashua, NH 03063
Phone: +1 978 206 9148 Phone: +1 781 442 3186
Email: chet.juszczak@sun.com Email: chet.juszczak@sun.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is
subject to the rights, licenses and restrictions contained in BCP
78 and except as set forth therein, the authors retain all their
rights.
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on
others, and derivative works that comment on or otherwise explain an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
it or assist in its implementation may be prepared, copied, REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
published and distributed, in whole or in part, without restriction THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
of any kind, provided that the above copyright notice and this EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
paragraph are included on all such copies and derivative works. THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
However, this document itself may not be modified in any way, such ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
as by removing the copyright notice or references to the Internet PARTICULAR PURPOSE.
Society or other Internet organizations, except as needed for the
purpose of developing Internet standards in which case the
procedures for copyrights defined in the Internet Standards process
must be followed, or as required to translate it into languages
other than English.
The limited permissions granted above are perpetual and will not be Intellectual Property
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on The IETF takes no position regarding the validity or scope of any
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET Intellectual Property Rights or other rights that might be claimed
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR to pertain to the implementation or use of the technology described
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF in this document or the extent to which any license under such
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED rights might or might not be available; nor does it represent that
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. it has made any independent effort to identify any such rights.
Information on the procedures with respect to rights in RFC
documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/