diff options
author | Stefan Priebe <s.priebe@profihost.ag> | 2013-11-16 20:26:52 (GMT) |
---|---|---|
committer | Kent Overstreet <kmo@daterainc.com> | 2013-12-16 22:04:57 (GMT) |
commit | f665c0f852316ff99e9eb7f71f34d43003f8e139 (patch) | |
tree | 000ab708468e8695a9762083cf5cb1d282a3d8b9 /drivers/md | |
parent | 08239ca2a053dbc3b082916bdfbd88e5a9ad9267 (diff) | |
download | linux-f665c0f852316ff99e9eb7f71f34d43003f8e139.tar.xz |
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>
Diffstat (limited to 'drivers/md')
-rw-r--r-- | drivers/md/bcache/writeback.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/md/bcache/writeback.c b/drivers/md/bcache/writeback.c index 99053b1..484e57d 100644 --- a/drivers/md/bcache/writeback.c +++ b/drivers/md/bcache/writeback.c @@ -500,8 +500,6 @@ int bch_cached_dev_writeback_init(struct cached_dev *dc) if (IS_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); schedule_delayed_work(&dc->writeback_rate_update, dc->writeback_rate_update_seconds * HZ); |