| Message ID | 20240325044452.3125418-28-dlemoal@kernel.org |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Zone write plugging | expand |
On 3/25/24 05:44, Damien Le Moal wrote: > 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> > --- > block/Kconfig | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/block/Kconfig b/block/Kconfig > index 9f647149fbee..d47398ae9824 100644 > --- a/block/Kconfig > +++ b/block/Kconfig > @@ -100,7 +100,6 @@ config BLK_DEV_WRITE_MOUNTED > > config BLK_DEV_ZONED > bool "Zoned block device support" > - select MQ_IOSCHED_DEADLINE > help > Block layer zoned block device support. This option enables > support for ZAC/ZBC/ZNS host-managed and host-aware zoned block Reviewed-by: Hannes Reinecke <hare@suse.de> Cheers, Hannes
diff --git a/block/Kconfig b/block/Kconfig index 9f647149fbee..d47398ae9824 100644 --- a/block/Kconfig +++ b/block/Kconfig @@ -100,7 +100,6 @@ config BLK_DEV_WRITE_MOUNTED config BLK_DEV_ZONED bool "Zoned block device support" - select MQ_IOSCHED_DEADLINE help Block layer zoned block device support. This option enables support for ZAC/ZBC/ZNS host-managed and host-aware zoned block
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> --- block/Kconfig | 1 - 1 file changed, 1 deletion(-)