diff options
| author |   Zhang Yi <yi.zhang@huawei.com> | 2025-04-23 16:52:50 +0800 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2025-05-14 10:42:12 -0400 |
| commit | 86b349ce0312a397a6961e457108556e44a3d211 (patch) | |
| tree | cb307214de8dc41efaacc35fcc6e8ee47840474d /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | ext4: ext4: unify EXT4_EX_NOCACHE|NOFAIL flags in ext4_ext_remove_space() (diff) | |
| download | wireguard-linux-86b349ce0312a397a6961e457108556e44a3d211.tar.xz wireguard-linux-86b349ce0312a397a6961e457108556e44a3d211.zip | |
ext4: generalize EXT4_GET_BLOCKS_IO_SUBMIT flag usage
Currently, the EXT4_GET_BLOCKS_IO_SUBMIT flag is only used during data
writeback to indicate that in ordered mode, the journal commit thread
should skip re-submitting data and simply wait for I/O completion.
To prepare for later patches that need to detect I/O submission context
in ext4_map_blocks(), generalizes the meaning of
EXT4_GET_BLOCKS_IO_SUBMIT. This flag will be set during:
1) data I/O writeback,
2) I/O completion extents conversion,
3) journal performing commit in fast_commit.
This change doesn't affect current usage of this flag and provides a
clear way to identify I/O submission context.
Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
Link: https://patch.msgid.link/20250423085257.122685-3-yi.zhang@huaweicloud.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions