diff options
author | Josef Bacik <josef@redhat.com> | 2012-04-12 22:03:57 +0200 |
---|---|---|
committer | Chris Mason <chris.mason@oracle.com> | 2012-04-13 02:54:01 +0200 |
commit | d53ba47484ed6245e640ee4bfe9d21e9bfc15765 (patch) | |
tree | 12bcb989f0e210f25770a72441eb8b947fd2fad3 /drivers/bluetooth/bcm203x.c | |
parent | Btrfs: fix use-after-free in __btrfs_end_transaction (diff) | |
download | linux-d53ba47484ed6245e640ee4bfe9d21e9bfc15765.tar.xz linux-d53ba47484ed6245e640ee4bfe9d21e9bfc15765.zip |
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 'drivers/bluetooth/bcm203x.c')
0 files changed, 0 insertions, 0 deletions