RFC 5664: Object-Based Parallel NFS (pNFS) Operations
In plain English — editorial summary, not part of the RFC
Parallel NFS (pNFS) extends Network File System version 4 (NFSv4) to allow clients to directly access file data on the storage used by the NFSv4 server. This ability to bypass the server for data access can increase both performance and parallelism, but requires additional client functionality for data access, some of which is dependent on the class of storage used, a.k.a. the Layout Type. The main pNFS operations and data types in NFSv4 Minor version 1 specify a layout- type-independent layer; layout-type-specific information is conveyed using opaque data structures whose internal structure is further defined by the particular layout type specification. This document specifies the NFSv4.1 Object-Based pNFS Layout Type as a companion to the main NFSv4 Minor version 1 specification. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5664
- Published
- January 2010
- Authors
- B. Halevy; B. Welch; J. Zelenka
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7143Internet Small Computer System Interface (iSCSI) Protocol (Consolidated)Current
April 2014
- RFC 5663Parallel NFS (pNFS) Block/Volume LayoutUpdated
January 2010
- RFC 5665IANA Considerations for Remote Procedure Call (RPC) Network Identifiers and Universal Address FormatsCurrent
January 2010
- RFC 5662Network File System (NFS) Version 4 Minor Version 1 External Data Representation Standard (XDR) DescriptionCurrent
January 2010
- RFC 5666Remote Direct Memory Access Transport for Remote Procedure CallObsoleted
January 2010
- RFC 5667Network File System (NFS) Direct Data PlacementObsoleted
January 2010
- RFC 5661Network File System (NFS) Version 4 Minor Version 1 ProtocolObsoleted
January 2010
- RFC 5681TCP Congestion ControlUpdated
September 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?