On 2018/3/7 12:07, Junling Zheng wrote: > Commit "0a007b97aad6"(f2fs: recover directory operations by fsync) > fixed xfstest generic/342 case, but it also increased the written > data and caused the performance degradation. In most cases, there's > no need to do so heavy fsync actually. > > So we introduce new mount option "fsync_mode={posix,strict}" to > control the policy of fsync. "fsync_mode=posix" is set by default, > and means that f2fs uses a light fsync, which follows POSIX semantics. > And "fsync_mode=strict" means that it's a heavy fsync, which behaves > in line with xfs, ext4 and btrfs, where generic/342 will pass, but > the performance will regress. > > Signed-off-by: Junling Zheng <zhengjunl...@huawei.com>
Reviewed-by: Chao Yu <yuch...@huawei.com> Thanks, ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel