aboutsummaryrefslogtreecommitdiff
path: root/fs/btrfs/scrub.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@redhat.com>2012-04-12 16:03:57 -0400
committerChris Mason <chris.mason@oracle.com>2012-04-12 20:54:01 -0400
commitd53ba47484ed6245e640ee4bfe9d21e9bfc15765 (patch)
tree12bcb989f0e210f25770a72441eb8b947fd2fad3 /fs/btrfs/scrub.c
parent4edc2ca388d62abffe38149f6ac00e749ea721c5 (diff)
downloadlinux-stericsson-d53ba47484ed6245e640ee4bfe9d21e9bfc15765.tar.gz
Btrfs: use commit root when loading free space cache
A user reported that booting his box up with btrfs root on 3.4 was way slower than on 3.3 because I removed the ideal caching code. It turns out that we don't load the free space cache if we're in a commit for deadlock reasons, but since we're reading the cache and it hasn't changed yet we are safe reading the inode and free space item from the commit root, so do that and remove all of the deadlock checks so we don't unnecessarily skip loading the free space cache. The user reported this fixed the slowness. Thanks, Tested-by: Calvin Walton <calvin.walton@kepstin.ca> Signed-off-by: Josef Bacik <josef@redhat.com> Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/scrub.c')
0 files changed, 0 insertions, 0 deletions