diff options
author | NeilBrown <neilb@suse.de> | 2015-02-19 06:04:40 +0100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2015-04-22 00:00:40 +0200 |
commit | 09314799e4f0589e52bafcd0ca3556c60468bc0e (patch) | |
tree | 012392cba7377a5db8c4c9e4c639337a6501cb46 /drivers/md/raid5.c | |
parent | md: don't require sync_min to be a multiple of chunk_size. (diff) | |
download | linux-09314799e4f0589e52bafcd0ca3556c60468bc0e.tar.xz linux-09314799e4f0589e52bafcd0ca3556c60468bc0e.zip |
md: remove 'go_faster' option from ->sync_request()
This option is not well justified and testing suggests that
it hardly ever makes any difference.
The comment suggests there might be a need to wait for non-resync
activity indicated by ->nr_waiting, however raise_barrier()
already waits for all of that.
So just remove it to simplify reasoning about speed limiting.
This allows us to remove a 'FIXME' comment from raid5.c as that
never used the flag.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to '')
-rw-r--r-- | drivers/md/raid5.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index cd2f96b2c572..022a0d99e110 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -5050,8 +5050,7 @@ ret: return reshape_sectors; } -/* FIXME go_faster isn't used */ -static inline sector_t sync_request(struct mddev *mddev, sector_t sector_nr, int *skipped, int go_faster) +static inline sector_t sync_request(struct mddev *mddev, sector_t sector_nr, int *skipped) { struct r5conf *conf = mddev->private; struct stripe_head *sh; |