summaryrefslogtreecommitdiff
path: root/fs/ext4/extents.c
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2012-04-16 12:16:20 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-22 15:30:59 -0700
commit23066aae743c617dcd1f77a64f6d44bebf87b097 (patch)
tree75db3403cb9c83529d8befc710d0de8f5c1fc1f3 /fs/ext4/extents.c
parent250a9e89bb62efc7719cc44f0e19536d58ab51d7 (diff)
ext4: address scalability issue by removing extent cache statistics
commit 9cd70b347e9761ea2d2ac3d758c529a48a8193e6 upstream. Andi Kleen and Tim Chen have reported that under certain circumstances the extent cache statistics are causing scalability problems due to cache line bounces. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ext4/extents.c')
-rw-r--r--fs/ext4/extents.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 75070365f479..c2a2012021a4 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -2052,10 +2052,6 @@ static int ext4_ext_check_cache(struct inode *inode, ext4_lblk_t block,
ret = 1;
}
errout:
- if (!ret)
- sbi->extent_cache_misses++;
- else
- sbi->extent_cache_hits++;
trace_ext4_ext_in_cache(inode, block, ret);
spin_unlock(&EXT4_I(inode)->i_block_reservation_lock);
return ret;