diff options
author | Damien Le Moal <[email protected]> | 2024-04-08 10:41:21 +0900 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2024-04-17 08:44:03 -0600 |
commit | fde02699c242e88a71286677d27cc890a959b67f (patch) | |
tree | d18a8e8ee0ca52196e17f33802a5fc06a48e3deb /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 9b3c08b90fc212de58c34621d83e74977170b2cd (diff) |
block: mq-deadline: Remove support for zone write locking
With the block layer generic plugging of write operations for zoned
block devices, mq-deadline, or any other scheduler, can only ever
see at most one write operation per zone at any time. There is thus no
sequentiality requirements for these writes and thus no need to tightly
control the dispatching of write requests using zone write locking.
Remove all the code that implement this control in the mq-deadline
scheduler and remove advertizing support for the
ELEVATOR_F_ZBD_SEQ_WRITE elevator feature.
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]>
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