aboutsummaryrefslogtreecommitdiff
path: root/block/blk-settings.c
diff options
context:
space:
mode:
authorGravatar Damien Le Moal <dlemoal@kernel.org> 2024-04-08 10:41:21 +0900
committerGravatar Jens Axboe <axboe@kernel.dk> 2024-04-17 08:44:03 -0600
commitfde02699c242e88a71286677d27cc890a959b67f (patch)
treed18a8e8ee0ca52196e17f33802a5fc06a48e3deb /block/blk-settings.c
parentblock: Simplify blk_revalidate_disk_zones() interface (diff)
downloadlinux-fde02699c242e88a71286677d27cc890a959b67f.tar.gz
linux-fde02699c242e88a71286677d27cc890a959b67f.tar.bz2
linux-fde02699c242e88a71286677d27cc890a959b67f.zip
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 <dlemoal@kernel.org> Reviewed-by: Hannes Reinecke <hare@suse.de> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Bart Van Assche <bvanassche@acm.org> Tested-by: Hans Holmberg <hans.holmberg@wdc.com> Tested-by: Dennis Maisenbacher <dennis.maisenbacher@wdc.com> Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com> Link: https://lore.kernel.org/r/20240408014128.205141-22-dlemoal@kernel.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-settings.c')
0 files changed, 0 insertions, 0 deletions