Commit 18d1aef8 authored by Christoph Hellwig's avatar Christoph Hellwig

nfsd: update documentation for pNFS support

Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
parent c5c707f9
...@@ -24,11 +24,6 @@ focuses on the mandatory-to-implement NFSv4.1 Sessions, providing ...@@ -24,11 +24,6 @@ focuses on the mandatory-to-implement NFSv4.1 Sessions, providing
"exactly once" semantics and better control and throttling of the "exactly once" semantics and better control and throttling of the
resources allocated for each client. resources allocated for each client.
Other NFSv4.1 features, Parallel NFS operations in particular,
are still under development out of tree.
See http://wiki.linux-nfs.org/wiki/index.php/PNFS_prototype_design
for more information.
The table below, taken from the NFSv4.1 document, lists The table below, taken from the NFSv4.1 document, lists
the operations that are mandatory to implement (REQ), optional the operations that are mandatory to implement (REQ), optional
(OPT), and NFSv4.0 operations that are required not to implement (MNI) (OPT), and NFSv4.0 operations that are required not to implement (MNI)
...@@ -43,9 +38,7 @@ The OPTIONAL features identified and their abbreviations are as follows: ...@@ -43,9 +38,7 @@ The OPTIONAL features identified and their abbreviations are as follows:
The following abbreviations indicate the linux server implementation status. The following abbreviations indicate the linux server implementation status.
I Implemented NFSv4.1 operations. I Implemented NFSv4.1 operations.
NS Not Supported. NS Not Supported.
NS* unimplemented optional feature. NS* Unimplemented optional feature.
P pNFS features implemented out of tree.
PNS pNFS features that are not supported yet (out of tree).
Operations Operations
...@@ -70,13 +63,13 @@ I | DESTROY_SESSION | REQ | | Section 18.37 | ...@@ -70,13 +63,13 @@ I | DESTROY_SESSION | REQ | | Section 18.37 |
I | EXCHANGE_ID | REQ | | Section 18.35 | I | EXCHANGE_ID | REQ | | Section 18.35 |
I | FREE_STATEID | REQ | | Section 18.38 | I | FREE_STATEID | REQ | | Section 18.38 |
| GETATTR | REQ | | Section 18.7 | | GETATTR | REQ | | Section 18.7 |
P | GETDEVICEINFO | OPT | pNFS (REQ) | Section 18.40 | I | GETDEVICEINFO | OPT | pNFS (REQ) | Section 18.40 |
P | GETDEVICELIST | OPT | pNFS (OPT) | Section 18.41 | NS*| GETDEVICELIST | OPT | pNFS (OPT) | Section 18.41 |
| GETFH | REQ | | Section 18.8 | | GETFH | REQ | | Section 18.8 |
NS*| GET_DIR_DELEGATION | OPT | DDELG (REQ) | Section 18.39 | NS*| GET_DIR_DELEGATION | OPT | DDELG (REQ) | Section 18.39 |
P | LAYOUTCOMMIT | OPT | pNFS (REQ) | Section 18.42 | I | LAYOUTCOMMIT | OPT | pNFS (REQ) | Section 18.42 |
P | LAYOUTGET | OPT | pNFS (REQ) | Section 18.43 | I | LAYOUTGET | OPT | pNFS (REQ) | Section 18.43 |
P | LAYOUTRETURN | OPT | pNFS (REQ) | Section 18.44 | I | LAYOUTRETURN | OPT | pNFS (REQ) | Section 18.44 |
| LINK | OPT | | Section 18.9 | | LINK | OPT | | Section 18.9 |
| LOCK | REQ | | Section 18.10 | | LOCK | REQ | | Section 18.10 |
| LOCKT | REQ | | Section 18.11 | | LOCKT | REQ | | Section 18.11 |
...@@ -122,9 +115,9 @@ Callback Operations ...@@ -122,9 +115,9 @@ Callback Operations
| | MNI | or OPT) | | | | MNI | or OPT) | |
+-------------------------+-----------+-------------+---------------+ +-------------------------+-----------+-------------+---------------+
| CB_GETATTR | OPT | FDELG (REQ) | Section 20.1 | | CB_GETATTR | OPT | FDELG (REQ) | Section 20.1 |
P | CB_LAYOUTRECALL | OPT | pNFS (REQ) | Section 20.3 | I | CB_LAYOUTRECALL | OPT | pNFS (REQ) | Section 20.3 |
NS*| CB_NOTIFY | OPT | DDELG (REQ) | Section 20.4 | NS*| CB_NOTIFY | OPT | DDELG (REQ) | Section 20.4 |
P | CB_NOTIFY_DEVICEID | OPT | pNFS (OPT) | Section 20.12 | NS*| CB_NOTIFY_DEVICEID | OPT | pNFS (OPT) | Section 20.12 |
NS*| CB_NOTIFY_LOCK | OPT | | Section 20.11 | NS*| CB_NOTIFY_LOCK | OPT | | Section 20.11 |
NS*| CB_PUSH_DELEG | OPT | FDELG (OPT) | Section 20.5 | NS*| CB_PUSH_DELEG | OPT | FDELG (OPT) | Section 20.5 |
| CB_RECALL | OPT | FDELG, | Section 20.2 | | CB_RECALL | OPT | FDELG, | Section 20.2 |
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment