NFS Direct Data Placement
draft-callaghan-nfsdirect-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brent Callaghan , Tom Talpey | ||
| Last updated | 2003-05-15 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 is available in these formats:
Abstract
The RDMA transport for ONC RPC supports direct data placement for NFS data. Direct data placement not only reduces the amount of data that needs to be copied in an NFS call, but allows much of the data movement over the network to be implemented in RDMA hardware. This draft describes the use of direct data placement by means of server- initiated RDMA Writes into client-supplied buffers in a Write list for implementations of NFS versions 2, 3, and 4 over an RDMA transport.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)