diff options
| author | NeilBrown <neilb@suse.de> | 2009-10-16 08:55:32 +0400 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2009-10-16 08:55:32 +0400 |
| commit | 1d9d52416c0445019ccc1f0fddb9a227456eb61b (patch) | |
| tree | 1dc189d68babe4827e2a16d98fae6aeaa40792d7 | |
| parent | 1442577bf6da1a31ae6555212202be9a2cec5642 (diff) | |
| download | linux-1d9d52416c0445019ccc1f0fddb9a227456eb61b.tar.xz | |
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>
| -rw-r--r-- | drivers/md/raid1.c | 1 | ||||
| -rw-r--r-- | drivers/md/raid10.c | 1 |
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); |