It's now makes sense to use elevator boot argument when blk-mq is in use,
since there is now a bunch of schedulers for it (deadline, kyber, bfq, none).

Signed-off-by: Alex Ivanov <[email protected]>
---
 block/elevator.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/block/elevator.c b/block/elevator.c
index 4bb2f0c93fa6..ef6b27f13dfd 100644
--- a/block/elevator.c
+++ b/block/elevator.c
@@ -208,12 +208,12 @@ int elevator_init(struct request_queue *q, char *name)
        }
 
        /*
-        * Use the default elevator specified by config boot param for
-        * non-mq devices, or by config option. Don't try to load modules
+        * Use the default elevator specified by config boot param
+        * or by config option. Don't try to load modules
         * as we could be running off async and request_module() isn't
         * allowed from async.
         */
-       if (!e && !q->mq_ops && *chosen_elevator) {
+       if (!e && *chosen_elevator) {
                e = elevator_get(chosen_elevator, false);
                if (!e)
                        printk(KERN_ERR "I/O scheduler %s not found\n",
-- 
2.13.2

Reply via email to