diff options
author | Bart Van Assche <bvanassche@acm.org> | 2021-08-05 19:42:00 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2021-08-05 19:49:21 +0200 |
commit | 2112f5c1330a671fa852051d85cb9eadc05d7eb7 (patch) | |
tree | a040f160f98f12a7c3b9006f3b93e8fbd33164a9 /block/Kconfig | |
parent | blk-mq: Introduce the BLK_MQ_F_NO_SCHED_BY_DEFAULT flag (diff) | |
download | linux-2112f5c1330a671fa852051d85cb9eadc05d7eb7.tar.xz linux-2112f5c1330a671fa852051d85cb9eadc05d7eb7.zip |
loop: Select I/O scheduler 'none' from inside add_disk()
We noticed that the user interface of Android devices becomes very slow
under memory pressure. This is because Android uses the zram driver on top
of the loop driver for swapping, because under memory pressure the swap
code alternates reads and writes quickly, because mq-deadline is the
default scheduler for loop devices and because mq-deadline delays writes by
five seconds for such a workload with default settings. Fix this by making
the kernel select I/O scheduler 'none' from inside add_disk() for loop
devices. This default can be overridden at any time from user space,
e.g. via a udev rule. This approach has an advantage compared to changing
the I/O scheduler from userspace from 'mq-deadline' into 'none', namely
that synchronize_rcu() does not get called.
This patch changes the default I/O scheduler for loop devices from
'mq-deadline' into 'none'.
Additionally, this patch reduces the Android boot time on my test setup
with 0.5 seconds compared to configuring the loop I/O scheduler from user
space.
Cc: Christoph Hellwig <hch@lst.de>
Cc: Ming Lei <ming.lei@redhat.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Martijn Coenen <maco@android.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Link: https://lore.kernel.org/r/20210805174200.3250718-3-bvanassche@acm.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/Kconfig')
0 files changed, 0 insertions, 0 deletions