[PATCH][DISCO][V2] UBUNTU: SAUCE: config: enable mq-deadline as default for multi-queue block I/O

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[PATCH][DISCO][V2] UBUNTU: SAUCE: config: enable mq-deadline as default for multi-queue block I/O

Colin King
From: Colin Ian King <[hidden email]>

There is compelling data showing that enabling the mq-deadline block I/O
scheduler as default for multi-queue devices is a sensible default. It
performs well across a range of I/O scenarios and is applicable for
various device drivers (null_blk, virtio-blk, mtip32xx, scsi_mq, NVMe,
rbd, ubiblock, loop, dm and dm-mpath).

For the moment, users who want to disable mq I/O scheduling can disable
this with a kernel boot parameter, for example for SCSI block devices
use: scsi_mod.use_blk_mq=0.  This will fall back to the I/O scheduler
defaults used in releases prior to 4.20 kernels in Ubuntu.

For non-multiqueue devices we currently fall back to the current
Ubuntu default of cfq, although at a later date I'd like to change
this too to deadline once the mq-deadline defaults have settled in.

Signed-off-by: Colin Ian King <[hidden email]>
---
 debian.master/config/config.common.ubuntu | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian.master/config/config.common.ubuntu b/debian.master/config/config.common.ubuntu
index 1d21a87..8c1015e 100644
--- a/debian.master/config/config.common.ubuntu
+++ b/debian.master/config/config.common.ubuntu
@@ -5730,7 +5730,7 @@ CONFIG_MPROFILE_KERNEL=y
 # CONFIG_MPSC is not set
 CONFIG_MPU3050=m
 CONFIG_MPU3050_I2C=m
-CONFIG_MQ_IOSCHED_DEADLINE=m
+CONFIG_MQ_IOSCHED_DEADLINE=y
 CONFIG_MQ_IOSCHED_KYBER=m
 CONFIG_MRP=m
 CONFIG_MS5611=m
--
2.7.4


--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team
Reply | Threaded
Open this post in threaded view
|

APPLIED: [PATCH][DISCO][V2] UBUNTU: SAUCE: config: enable mq-deadline as default for multi-queue block I/O

Seth Forshee
On Tue, Dec 11, 2018 at 01:09:42PM +0000, Colin King wrote:

> From: Colin Ian King <[hidden email]>
>
> There is compelling data showing that enabling the mq-deadline block I/O
> scheduler as default for multi-queue devices is a sensible default. It
> performs well across a range of I/O scenarios and is applicable for
> various device drivers (null_blk, virtio-blk, mtip32xx, scsi_mq, NVMe,
> rbd, ubiblock, loop, dm and dm-mpath).
>
> For the moment, users who want to disable mq I/O scheduling can disable
> this with a kernel boot parameter, for example for SCSI block devices
> use: scsi_mod.use_blk_mq=0.  This will fall back to the I/O scheduler
> defaults used in releases prior to 4.20 kernels in Ubuntu.
>
> For non-multiqueue devices we currently fall back to the current
> Ubuntu default of cfq, although at a later date I'd like to change
> this too to deadline once the mq-deadline defaults have settled in.
>
> Signed-off-by: Colin Ian King <[hidden email]>

Applied to disco/master-next and unstable/master, thanks!

--
kernel-team mailing list
[hidden email]
https://lists.ubuntu.com/mailman/listinfo/kernel-team