summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorDamien Le Moal <dlemoal@kernel.org>2024-04-11 11:55:02 +0300
committerJens Axboe <axboe@kernel.dk>2024-04-17 17:44:07 +0300
commite994ff5b55e3bf30ecb6ed354eaec77c989aa4ae (patch)
treec44200859a82ddead58fc5a16ef04814755bbc05 /tools/perf/scripts/python/export-to-postgresql.py
parent3bdde0701e5f819df0fa0e32fa8d5df7dc184cb5 (diff)
downloadlinux-e994ff5b55e3bf30ecb6ed354eaec77c989aa4ae.tar.xz
null_blk: Simplify null_zone_write()
In null_zone_write, we do not need to first check if the target zone condition is FULL, READONLY or OFFLINE: for theses conditions, the check of the command sector against the zone write pointer will always result in the command failing. Remove these checks. We still however need to check that the target zone write pointer is not invalid for zone append operations. To do so, add the macro NULL_ZONE_INVALID_WP and use it in null_set_zone_cond() when changing a zone to READONLY or OFFLINE condition. Signed-off-by: Damien Le Moal <dlemoal@kernel.org> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Link: https://lore.kernel.org/r/20240411085502.728558-4-dlemoal@kernel.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions