aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/c++/clang-test.cpp
diff options
context:
space:
mode:
authorJaegeuk Kim <[email protected]>2019-11-26 15:01:42 -0800
committerJaegeuk Kim <[email protected]>2019-12-09 15:57:45 -0800
commit47501f87c61ad2aa234add63e1ae231521dbc3f5 (patch)
tree5c5db98f65d8d23b20ccc9a7512f36b4ea35ee8f /tools/perf/util/c++/clang-test.cpp
parent6794862a16ef41f753abd75c03a152836e4c8028 (diff)
f2fs: preallocate DIO blocks when forcing buffered_io
The previous preallocation and DIO decision like below. allow_outplace_dio !allow_outplace_dio f2fs_force_buffered_io (*) No_Prealloc / Buffered_IO Prealloc / Buffered_IO !f2fs_force_buffered_io No_Prealloc / DIO Prealloc / DIO But, Javier reported Case (*) where zoned device bypassed preallocation but fell back to buffered writes in f2fs_direct_IO(), resulting in stale data being read. In order to fix the issue, actually we need to preallocate blocks whenever we fall back to buffered IO like this. No change is made in the other cases. allow_outplace_dio !allow_outplace_dio f2fs_force_buffered_io (*) Prealloc / Buffered_IO Prealloc / Buffered_IO !f2fs_force_buffered_io No_Prealloc / DIO Prealloc / DIO Reported-and-tested-by: Javier Gonzalez <[email protected]> Signed-off-by: Damien Le Moal <[email protected]> Tested-by: Shin'ichiro Kawasaki <[email protected]> Reviewed-by: Chao Yu <[email protected]> Reviewed-by: Javier González <[email protected]> Signed-off-by: Jaegeuk Kim <[email protected]>
Diffstat (limited to 'tools/perf/util/c++/clang-test.cpp')
0 files changed, 0 insertions, 0 deletions