nfsd4: better estimate of getattr response size
authorJ. Bruce Fields <bfields@redhat.com>
Sun, 23 Mar 2014 16:01:48 +0000 (12:01 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Fri, 30 May 2014 21:32:06 +0000 (17:32 -0400)
commitb86cef60dafcbdf5a19adfa990c2c1672222e677
tree46e1a02bc88ba8f9c56f1c9613bb0092448d4783
parent476a7b1f4b2c9c38255653fa55157565be8b14be
nfsd4: better estimate of getattr response size

We plan to use this estimate to decide whether or not to allow zero-copy
reads.  Currently we're assuming all getattr's are a page, which can be
both too small (ACLs e.g. may be arbitrarily long) and too large (after
an upcoming read patch this will unnecessarily prevent zero copy reads
in any read compound also containing a getattr).

Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4proc.c