summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid10.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-12-14 12:49:54 +1100
committerNeilBrown <neilb@suse.de>2009-12-14 12:51:41 +1100
commit9cd30fdc33cde9ae4ac55a1ccbbb89f3f7b9b2f2 (patch)
treeb6a4e0303fe3261892f24f26d7ecebf06a6be1a9 /drivers/md/raid10.c
parent1b04be96f6910ee415287bf0d5309c7d4c94bd2b (diff)
downloadblackbird-op-linux-9cd30fdc33cde9ae4ac55a1ccbbb89f3f7b9b2f2.tar.gz
blackbird-op-linux-9cd30fdc33cde9ae4ac55a1ccbbb89f3f7b9b2f2.zip
md: remove needless setting of thread->timeout in raid10_quiesce
As bitmap_create and bitmap_destroy already set thread->timeout as appropriate, there is no need to do it in raid10_quiesce. There is a possible need to wake the thread after the timeout has been set low, but it is better to do that where the timeout is actually set low, in bitmap_create. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid10.c')
-rw-r--r--drivers/md/raid10.c7
1 files changed, 0 insertions, 7 deletions
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index 064c2bb5ee63..d9e28a65af58 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -2275,13 +2275,6 @@ static void raid10_quiesce(mddev_t *mddev, int state)
lower_barrier(conf);
break;
}
- if (mddev->thread) {
- if (mddev->bitmap)
- mddev->thread->timeout = mddev->bitmap_info.daemon_sleep;
- else
- mddev->thread->timeout = MAX_SCHEDULE_TIMEOUT;
- md_wakeup_thread(mddev->thread);
- }
}
static struct mdk_personality raid10_personality =
OpenPOWER on IntegriCloud