Skip to content

Commit 97abee5

Browse files
damien-lemoalaxboe
authored andcommitted
block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED
Now that zone block device write ordering control does not depend anymore on mq-deadline and zone write locking, there is no need to force select the mq-deadline scheduler when CONFIG_BLK_DEV_ZONED is enabled. Signed-off-by: Damien Le Moal <dlemoal@kernel.org> Reviewed-by: Bart Van Assche <bvanassche@acm.org> Reviewed-by: Hannes Reinecke <hare@suse.de> Reviewed-by: Christoph Hellwig <hch@lst.de> 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-28-dlemoal@kernel.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
1 parent 02ccd7c commit 97abee5

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

block/Kconfig

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,6 @@ config BLK_DEV_WRITE_MOUNTED
100100

101101
config BLK_DEV_ZONED
102102
bool "Zoned block device support"
103-
select MQ_IOSCHED_DEADLINE
104103
help
105104
Block layer zoned block device support. This option enables
106105
support for ZAC/ZBC/ZNS host-managed and host-aware zoned block

0 commit comments

Comments
 (0)