diff options
| author | Josef Bacik | 2010-03-19 19:07:23 +0100 |
|---|---|---|
| committer | Chris Mason | 2010-03-31 03:19:09 +0200 |
| commit | 287a0ab91d25ca982f895a76402e5893b47ed7a6 (patch) | |
| tree | fcbe35daef2b4cbdc2bfc0c6026e7c45faef0245 /fs/btrfs/extent-tree.c | |
| parent | Btrfs: fail to mount if we have problems reading the block groups (diff) | |
| download | kernel-qcow2-linux-287a0ab91d25ca982f895a76402e5893b47ed7a6.tar.gz kernel-qcow2-linux-287a0ab91d25ca982f895a76402e5893b47ed7a6.tar.xz kernel-qcow2-linux-287a0ab91d25ca982f895a76402e5893b47ed7a6.zip | |
Btrfs: kill max_extent mount option
As Yan pointed out, theres not much reason for all this complicated math to
account for file extents being split up into max_extent chunks, since they are
likely to all end up in the same leaf anyway. Since there isn't much reason to
use max_extent, just remove the option altogether so we have one less thing we
need to test.
Signed-off-by: Josef Bacik <josef@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/extent-tree.c')
| -rw-r--r-- | fs/btrfs/extent-tree.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index 4c910359c807..5f6bc283c0c8 100644 --- a/fs/btrfs/extent-tree.c +++ b/fs/btrfs/extent-tree.c @@ -2846,7 +2846,7 @@ int btrfs_unreserve_metadata_for_delalloc(struct btrfs_root *root, } spin_unlock(&BTRFS_I(inode)->accounting_lock); - BTRFS_I(inode)->reserved_extents--; + BTRFS_I(inode)->reserved_extents -= num_items; BUG_ON(BTRFS_I(inode)->reserved_extents < 0); if (meta_sinfo->bytes_delalloc < num_bytes) { @@ -3111,7 +3111,7 @@ again: return -ENOSPC; } - BTRFS_I(inode)->reserved_extents++; + BTRFS_I(inode)->reserved_extents += num_items; check_force_delalloc(meta_sinfo); spin_unlock(&meta_sinfo->lock); |