diff options
author | Dave Chinner <dchinner@redhat.com> | 2012-03-22 05:15:10 +0000 |
---|---|---|
committer | Ben Myers <bpm@sgi.com> | 2012-03-26 17:19:08 -0500 |
commit | 5132ba8f2b7705fb6b06fa6ad3d009233c816b67 (patch) | |
tree | e552a365b600af005abec13f3a1deb1f57bae3b9 /fs/block_dev.c | |
parent | f616137519feb17b849894fcbe634a021d3fa7db (diff) | |
download | linux-5132ba8f2b7705fb6b06fa6ad3d009233c816b67.tar.gz linux-5132ba8f2b7705fb6b06fa6ad3d009233c816b67.tar.bz2 linux-5132ba8f2b7705fb6b06fa6ad3d009233c816b67.zip |
xfs: don't cache inodes read through bulkstat
When we read inodes via bulkstat, we generally only read them once
and then throw them away - they never get used again. If we retain
them in cache, then it simply causes the working set of inodes and
other cached items to be reclaimed just so the inode cache can grow.
Avoid this problem by marking inodes read by bulkstat not to be
cached and check this flag in .drop_inode to determine whether the
inode should be added to the VFS LRU or not. If the inode lookup
hits an already cached inode, then don't set the flag. If the inode
lookup hits an inode marked with no cache flag, remove the flag and
allow it to be cached once the current reference goes away.
Inodes marked as not cached will get cleaned up by the background
inode reclaim or via memory pressure, so they will still generate
some short term cache pressure. They will, however, be reclaimed
much sooner and in preference to cache hot inodes.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/block_dev.c')
0 files changed, 0 insertions, 0 deletions