summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorNeil Brown <neilb@cse.unsw.edu.au>2003-02-17 03:16:37 -0800
committerJames Bottomley <jejb@raven.il.steeleye.com>2003-02-17 03:16:37 -0800
commit467cb27b15d3419a027443119298311e2f851b8f (patch)
tree6645d824b14d71026c022358c417ac508fcc9771 /include/linux
parent2aeb031101ec46b32cf8411e99bb1d3398829fda (diff)
[PATCH] Keep track of which page is the 'tail' of an NFSd reply
NFS replies can have a 'tail' after a 'data' component (for read, readlink, readdir). For nfsv2 and v3 this tail is in the same page as the head. For nfsv4, this tail is in a separate page. We need to keep track of which page so that it right one gets sent. This patch does that.
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/sunrpc/svc.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/sunrpc/svc.h b/include/linux/sunrpc/svc.h
index 9408ba6dbe34..6553637b70ee 100644
--- a/include/linux/sunrpc/svc.h
+++ b/include/linux/sunrpc/svc.h
@@ -114,6 +114,7 @@ struct svc_rqst {
struct xdr_buf rq_res;
struct page * rq_argpages[RPCSVC_MAXPAGES];
struct page * rq_respages[RPCSVC_MAXPAGES];
+ int rq_restailpage;
short rq_argused; /* pages used for argument */
short rq_arghi; /* pages available in argument page list */
short rq_resused; /* pages used for result */