diff options
| author | J. Bruce Fields <bfields@redhat.com> | 2014-03-18 22:44:10 +0100 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2014-05-30 23:32:12 +0200 |
| commit | b042098063849794d69b5322fcc6cf9fb5f2586e (patch) | |
| tree | 954338c0f2de77763df3e8728265b91842984466 /Documentation/filesystems | |
| parent | nfsd4: more read encoding cleanup (diff) | |
| download | linux-b042098063849794d69b5322fcc6cf9fb5f2586e.tar.xz linux-b042098063849794d69b5322fcc6cf9fb5f2586e.zip | |
nfsd4: allow exotic read compounds
I'm not sure why a client would want to stuff multiple reads in a
single compound rpc, but it's legal for them to do it, and we should
really support it.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'Documentation/filesystems')
| -rw-r--r-- | Documentation/filesystems/nfs/nfs41-server.txt | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/Documentation/filesystems/nfs/nfs41-server.txt b/Documentation/filesystems/nfs/nfs41-server.txt index b930ad087780..c49cd7e796e7 100644 --- a/Documentation/filesystems/nfs/nfs41-server.txt +++ b/Documentation/filesystems/nfs/nfs41-server.txt @@ -176,7 +176,5 @@ Nonstandard compound limitations: ca_maxrequestsize request and a ca_maxresponsesize reply, so we may fail to live up to the promise we made in CREATE_SESSION fore channel negotiation. -* No more than one read-like operation allowed per compound; encoding - replies that cross page boundaries (except for read data) not handled. See also http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues. |