btrfs: remove struct find_free_extent.ram_bytes

This hasn't been used since it was first introduced in commit
91b68fbe4304 ("btrfs: Introduce find_free_extent_ctl structure for later
rework"). Passing that to btrfs_add_reserved_bytes in find_free_extent
is not strictly necessary and using the local ram_bytes instead seems
cleaner.

Signed-off-by: Omar Sandoval <osandov@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>

diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 2a7dff22c3b743c132bce492498d609c8a6f2674..180b9b81d01aa02a53fd2fbb7d04585a46a52c8d 100644 (file)
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -3438,7 +3438,6 @@ btrfs_release_block_group(struct btrfs_block_group *cache,
  */
 struct find_free_extent_ctl {
        /* Basic allocation info */
-       u64 ram_bytes;
        u64 num_bytes;
        u64 empty_size;
        u64 flags;
@@ -3810,7 +3809,6 @@ static noinline int find_free_extent(struct btrfs_fs_info *fs_info,
 
        WARN_ON(num_bytes < fs_info->sectorsize);
 
-       ffe_ctl.ram_bytes = ram_bytes;
        ffe_ctl.num_bytes = num_bytes;
        ffe_ctl.empty_size = empty_size;
        ffe_ctl.flags = flags;