We currently suspend rather large sections of
the array which can take a while to process.
Possibly smaller sections are better. Possibly it should be
adjusted on a timeout basis.
Signed-off-by: NeilBrown <neilb@suse.de>
* Consider extending suspend_point 128M per device if it
* is less than 64M per device beyond reshape_progress.
* But always do a multiple of 'blocks'
+ * FIXME this is too big - it takes to long to complete
+ * this much.
*/
target = 64*1024*2 * min(reshape->before.data_disks,
reshape->after.data_disks);