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>

1 files changed, 2 insertions, 3 deletions

diff --git a/drivers/md/md.c b/drivers/md/md.c
index 3724a29eaf0e..3b9b032aa006 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -7820,8 +7820,7 @@ void md_do_sync(struct md_thread *thread)
                 if (test_bit(MD_RECOVERY_INTR, &mddev->recovery))
                         break;
 
-                sectors = mddev->pers->sync_request(mddev, j, &skipped,
-                                                  currspeed < speed_min(mddev));
+                sectors = mddev->pers->sync_request(mddev, j, &skipped);
                 if (sectors == 0) {
                         set_bit(MD_RECOVERY_INTR, &mddev->recovery);
                         break;
@@ -7898,7 +7897,7 @@ void md_do_sync(struct md_thread *thread)
         wait_event(mddev->recovery_wait, !atomic_read(&mddev->recovery_active));
 
         /* tell personality that we are finished */
-        mddev->pers->sync_request(mddev, max_sectors, &skipped, 1);
+        mddev->pers->sync_request(mddev, max_sectors, &skipped);
 
         if (mddev_is_clustered(mddev))
                 md_cluster_ops->resync_finish(mddev);