diff options
author | Rajesh Ghanekar <Rajesh_Ghanekar@symantec.com> | 2014-08-01 22:17:30 -0400 |
---|---|---|
committer | J. Bruce Fields <bfields@redhat.com> | 2014-08-18 15:12:14 -0400 |
commit | 18c01ab30288d9d0a7d80b08b659531f37ed379d (patch) | |
tree | 327704befb41873e859ae20574f7eda538ac3670 /mm/slub.c | |
parent | f7b43d0c992c3ec3e8d9285c3fb5e1e0eb0d031a (diff) | |
download | op-kernel-dev-18c01ab30288d9d0a7d80b08b659531f37ed379d.zip op-kernel-dev-18c01ab30288d9d0a7d80b08b659531f37ed379d.tar.gz |
nfsd: allow turning off nfsv3 readdir_plus
One of our customer's application only needs file names, not file
attributes. With directories having 10K+ inodes (assuming buffer cache
has directory blocks cached having file names, but inode cache is
limited and hence need eviction of older cached inodes), older inodes
are evicted periodically. So if they keep on doing readdir(2) from NSF
client on multiple directories, some directory's files are periodically
removed from inode cache and hence new readdir(2) on same directory
requires disk access to bring back inodes again to inode cache.
As READDIRPLUS request fetches attributes also, doing getattr on each
file on server, it causes unnecessary disk accesses. If READDIRPLUS on
NFS client is returned with -ENOTSUPP, NFS client uses READDIR request
which just gets the names of the files in a directory, not attributes,
hence avoiding disk accesses on server.
There's already a corresponding client-side mount option, but an export
option reduces the need for configuration across multiple clients.
This flag affects NFSv3 only. If it turns out it's needed for NFSv4 as
well then we may have to figure out how to extend the behavior to NFSv4,
but it's not currently obvious how to do that.
Signed-off-by: Rajesh Ghanekar <rajesh_ghanekar@symantec.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'mm/slub.c')
0 files changed, 0 insertions, 0 deletions