diff options
| author | J. Bruce Fields <bfields@redhat.com> | 2011-01-24 17:11:02 (GMT) |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2011-07-18 13:39:01 (GMT) |
| commit | 1091006c5eb15cba56785bd5b498a8d0b9546903 (patch) | |
| tree | b51fad1bb57284b3eea4308c02652c4888b85860 /fs/nfsd/xdr4.h | |
| parent | 3e98abffd1665b884a322aedcd528577842f762f (diff) | |
| download | linux-1091006c5eb15cba56785bd5b498a8d0b9546903.tar.xz | |
nfsd: turn on reply cache for NFSv4
It's sort of ridiculous that we've never had a working reply cache for
NFSv4.
On the other hand, we may still not: our current reply cache is likely
not very good, especially in the TCP case (which is the only case that
matters for v4). What we really need here is some serious testing.
Anyway, here's a start.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd/xdr4.h')
| -rw-r--r-- | fs/nfsd/xdr4.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/fs/nfsd/xdr4.h b/fs/nfsd/xdr4.h index 351348c..d2a8d044 100644 --- a/fs/nfsd/xdr4.h +++ b/fs/nfsd/xdr4.h @@ -457,6 +457,8 @@ struct nfsd4_op { struct nfs4_replay * replay; }; +bool nfsd4_cache_this_op(struct nfsd4_op *); + struct nfsd4_compoundargs { /* scratch variables for XDR decode */ __be32 * p; @@ -479,6 +481,7 @@ struct nfsd4_compoundargs { u32 opcnt; struct nfsd4_op *ops; struct nfsd4_op iops[8]; + int cachetype; }; struct nfsd4_compoundres { |