NFS RDMA Problem Statement
draft-talpey-nfs-rdma-problem-statement-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Tom Talpey | ||
| Last updated | 2004-02-12 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-talpey-nfs-rdma-problem-statement-01.txt
https://www.ietf.org/archive/id/draft-talpey-nfs-rdma-problem-statement-01.txt
Abstract
This draft addresses applying Remote Direct Memory Access to the NFS protocols. NFS implementations historically incur significant overhead due to data copies on end-host systems, as well as other sources. The potential benefits of RDMA to these implementations are explored, and the reasons why RDMA is especially well-suited to NFS and network file protocols in general are evaluated.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)