bcache: kthread don't set writeback task to INTERUPTIBLE
at the beginning (schedule_timout_interuptible) and others do his on their own This prevents wrong load average calculation (load of 1 per thread) Signed-off-by: Kent Overstreet <kmo@daterainc.com>
This commit is contained in:
Родитель
08239ca2a0
Коммит
f665c0f852
|
@ -500,8 +500,6 @@ int bch_cached_dev_writeback_init(struct cached_dev *dc)
|
||||||
if (IS_ERR(dc->writeback_thread))
|
if (IS_ERR(dc->writeback_thread))
|
||||||
return PTR_ERR(dc->writeback_thread);
|
return PTR_ERR(dc->writeback_thread);
|
||||||
|
|
||||||
set_task_state(dc->writeback_thread, TASK_INTERRUPTIBLE);
|
|
||||||
|
|
||||||
INIT_DELAYED_WORK(&dc->writeback_rate_update, update_writeback_rate);
|
INIT_DELAYED_WORK(&dc->writeback_rate_update, update_writeback_rate);
|
||||||
schedule_delayed_work(&dc->writeback_rate_update,
|
schedule_delayed_work(&dc->writeback_rate_update,
|
||||||
dc->writeback_rate_update_seconds * HZ);
|
dc->writeback_rate_update_seconds * HZ);
|
||||||
|
|
Загрузка…
Ссылка в новой задаче