diff options
author | LiFan <fanofcode.li@samsung.com> | 2017-12-05 16:38:01 +0800 |
---|---|---|
committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2018-01-02 19:27:30 -0800 |
commit | fab2adee36039cdc2002ba3fe3a416c3f1bc6b52 (patch) | |
tree | 2a5916b9c99cf68ab6b63c2435c58258a6733912 /fs/f2fs | |
parent | f652e9d988d6b4d2a81c920374431a73b70090fd (diff) | |
download | linux-fab2adee36039cdc2002ba3fe3a416c3f1bc6b52.tar.bz2 |
f2fs: use unlikely for release case
Since the variable release is only nonzero when another unlikely
case occurs, use unlikely() on it seems logical.
Signed-off-by: Fan li <fanofcode.li@samsung.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs')
-rw-r--r-- | fs/f2fs/f2fs.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index e9e72844220c..930cf430dcc2 100644 --- a/fs/f2fs/f2fs.h +++ b/fs/f2fs/f2fs.h @@ -1594,7 +1594,7 @@ static inline int inc_valid_block_count(struct f2fs_sb_info *sbi, } spin_unlock(&sbi->stat_lock); - if (release) + if (unlikely(release)) dquot_release_reservation_block(inode, release); f2fs_i_blocks_write(inode, *count, true, true); return 0; |