diff options
author | Coly Li | 2019-06-28 13:59:24 +0200 |
---|---|---|
committer | Jens Axboe | 2019-06-28 15:39:13 +0200 |
commit | 141df8bb5dc052f605de8f48a7aa10290e1384ae (patch) | |
tree | 355b2bb99b0584a0f09c00304e4e5b2252f5bb9f /sound/core/seq/seq_midi_event.c | |
parent | block: Remove unused code (diff) | |
download | kernel-qcow2-linux-141df8bb5dc052f605de8f48a7aa10290e1384ae.tar.gz kernel-qcow2-linux-141df8bb5dc052f605de8f48a7aa10290e1384ae.tar.xz kernel-qcow2-linux-141df8bb5dc052f605de8f48a7aa10290e1384ae.zip |
bcache: don't set max writeback rate if gc is running
When gc is running, user space I/O processes may wait inside
bcache code, so no new I/O coming. Indeed this is not a real idle
time, maximum writeback rate should not be set in such situation.
Otherwise a faster writeback thread may compete locks with gc thread
and makes garbage collection slower, which results a longer I/O
freeze period.
This patch checks c->gc_mark_valid in set_at_max_writeback_rate(). If
c->gc_mark_valid is 0 (gc running), set_at_max_writeback_rate() returns
false, then update_writeback_rate() will not set writeback rate to
maximum value even c->idle_counter reaches an idle threshold.
Now writeback thread won't interfere gc thread performance.
Signed-off-by: Coly Li <colyli@suse.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'sound/core/seq/seq_midi_event.c')
0 files changed, 0 insertions, 0 deletions