diff options
| author | Filipe Manana <fdmanana@suse.com> | 2022-10-11 15:16:58 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2022-12-05 20:00:38 +0300 |
| commit | 206c1d32f381ee91ba849a7dcb28728e8c3721b6 (patch) | |
| tree | 30c69bc2a7b1c48cfa5dd62e8280e1041d2f370d | |
| parent | b98c6cd59e90fe659cf966859bc4e1c03aea347b (diff) | |
| download | linux-206c1d32f381ee91ba849a7dcb28728e8c3721b6.tar.xz | |
btrfs: drop redundant bflags initialization when allocating extent buffer
When allocating an extent buffer, at __alloc_extent_buffer(), there's no
point in explicitly assigning zero to the bflags field of the new extent
buffer because we allocated it with kmem_cache_zalloc().
So just remove the redundant initialization, it saves one mov instruction
in the generated assembly code for x86_64 ("movq $0x0,0x10(%rax)").
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
| -rw-r--r-- | fs/btrfs/extent_io.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c index 56a9f591f479..3192f094fe6c 100644 --- a/fs/btrfs/extent_io.c +++ b/fs/btrfs/extent_io.c @@ -4266,7 +4266,6 @@ __alloc_extent_buffer(struct btrfs_fs_info *fs_info, u64 start, eb->start = start; eb->len = len; eb->fs_info = fs_info; - eb->bflags = 0; init_rwsem(&eb->lock); btrfs_leak_debug_add_eb(eb); |