f2fs: use unlikely for release case
authorLiFan <fanofcode.li@samsung.com>
Tue, 5 Dec 2017 08:38:01 +0000 (16:38 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Sat, 27 Jan 2018 21:29:35 +0000 (13:29 -0800)
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>
fs/f2fs/f2fs.h

index 82f1dc34550586175b82200eb3a909f6bd470d21..6c6cf94f490ff7e6209ea5fcf2cd3181edcb2c24 100644 (file)
@@ -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;