NFS Version 4 Minor Version 2 unstable file creation and attribute update improvements
draft-myklebust-nfsv42-unstable-file-creation-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Trond Myklebust | ||
| Last updated | 2010-10-17 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
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) |
https://www.ietf.org/archive/id/draft-myklebust-nfsv42-unstable-file-creation-00.txt
Abstract
This document describes an extension to the NFSv4 protocol to allow clients to create and write files with greater efficiency. The first proposal allows the server to defer creating the file on stable storage when replying to an OPEN call. The aim is to improve server efficiency and scalability by reducing the number of required disk accesses when writing a file from scratch. The second proposal allows the server to share information about the implementation of its change attribute with the client. The aim is to improve the client's ability to determine the order in which parallel updates to the same file were processed.Keywords The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)