diff options
author | Damien Le Moal <[email protected]> | 2024-04-08 10:41:15 +0900 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2024-04-17 08:44:03 -0600 |
commit | b66f79b706f0cfc09bde8465668428eef188a94c (patch) | |
tree | 751710c14b9caae7af56e00ac04c7d640048d89a /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 11be0cb5fe25603472831f85abb32f0112239238 (diff) |
null_blk: Do not request ELEVATOR_F_ZBD_SEQ_WRITE elevator feature
With zone write plugging enabled at the block layer level, a zoned
device can only ever see at most a single write operation per zone.
There is thus no need to request a block scheduler with strick per-zone
sequential write ordering control through the ELEVATOR_F_ZBD_SEQ_WRITE
feature. Removing this allows using a zoned null_blk device with any
scheduler, including "none".
Signed-off-by: Damien Le Moal <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Reviewed-by: Bart Van Assche <[email protected]>
Reviewed-by: Chaitanya Kulkarni <[email protected]>
Tested-by: Hans Holmberg <[email protected]>
Tested-by: Dennis Maisenbacher <[email protected]>
Reviewed-by: Martin K. Petersen <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions