summaryrefslogtreecommitdiffstats
path: root/fs/ext4/extents.c
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2012-04-16 18:16:20 +0200
committerTheodore Ts'o <tytso@mit.edu>2012-04-16 18:16:20 +0200
commit9cd70b347e9761ea2d2ac3d758c529a48a8193e6 (patch)
treef215d10558a62c34aff4528f1c40f1b154bd6c25 /fs/ext4/extents.c
parentLinux 3.4-rc2 (diff)
downloadlinux-9cd70b347e9761ea2d2ac3d758c529a48a8193e6.tar.xz
linux-9cd70b347e9761ea2d2ac3d758c529a48a8193e6.zip
ext4: address scalability issue by removing extent cache statistics
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> Cc: stable@vger.kernel.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 1421938e6792..8a12cd207679 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -2066,10 +2066,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;