Support for posix_fadvise
draft-hildebrand-nfsv4-fadvise-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dean Hildebrand , Trond Myklebust , Sam Falkner | ||
| Last updated | 2011-07-07 | ||
| 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
This document proposes a new FADVISE operation for NFSv4.2 to support the posix_fadvise function. FADVISE will communicate expected application behavior to the server, allowing servers to optimize future I/O requests for a file. The posix_fadvise function is supported in Linux and many other operating systems and is starting be widely used by applications. In addition, the FADVISE operation can communicate other application directions such as the use of direct I/O.
Authors
Dean Hildebrand
Trond Myklebust
Sam Falkner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)