summaryrefslogtreecommitdiffstats
path: root/drivers/md
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-10-16 06:55:32 +0200
committerNeilBrown <neilb@suse.de>2009-10-16 06:55:32 +0200
commit1d9d52416c0445019ccc1f0fddb9a227456eb61b (patch)
tree1dc189d68babe4827e2a16d98fae6aeaa40792d7 /drivers/md
parentRevert "md: do not progress the resync process if the stripe was blocked" (diff)
downloadlinux-1d9d52416c0445019ccc1f0fddb9a227456eb61b.tar.xz
linux-1d9d52416c0445019ccc1f0fddb9a227456eb61b.zip
md/raid1/raid10: add a cond_resched
During 'check' of a raid1 or raid10 it is possible for the management thread to spend a lot of time running 'memcmp' on blocks from different devices, so make sure the thread has a chance to schedule. raid5d already has a cond_resched (in process_stripe). Reported-By: Lee Howard <faxguy@howardsilvan.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md')
-rw-r--r--drivers/md/raid1.c1
-rw-r--r--drivers/md/raid10.c1
2 files changed, 2 insertions, 0 deletions
diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c
index d1b9bd5fd4f6..71a01a2e1938 100644
--- a/drivers/md/raid1.c
+++ b/drivers/md/raid1.c
@@ -1683,6 +1683,7 @@ static void raid1d(mddev_t *mddev)
generic_make_request(bio);
}
}
+ cond_resched();
}
if (unplug)
unplug_slaves(mddev);
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index 51c4c5c4d87a..69fc76caa469 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -1632,6 +1632,7 @@ static void raid10d(mddev_t *mddev)
generic_make_request(bio);
}
}
+ cond_resched();
}
if (unplug)
unplug_slaves(mddev);