This is always triggered for small reads preventing spreading the reads across all available drives. The comments are also confusing as it is supposed to apply only to 'far' layouts, but really only applies to 'near' layouts. Since there isn't problems with 'far' layouts, there shouldn't be a problem for 'near' layouts either. This change fairly distributes reads across all drives where before only came from the first drive. Signed-off-by: Robert LeBlanc <robert@xxxxxxxxxxxxx> --- drivers/md/raid10.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index be1a9fc..8d83802 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -777,13 +777,6 @@ static struct md_rdev *read_balance(struct r10conf *conf, if (!do_balance) break; - /* This optimisation is debatable, and completely destroys - * sequential read speed for 'far copies' arrays. So only - * keep it for 'near' arrays, and review those later. - */ - if (geo->near_copies > 1 && !atomic_read(&rdev->nr_pending)) - break; - /* for far > 1 always use the lowest address */ if (geo->far_copies > 1) new_distance = r10_bio->devs[slot].addr; -- 2.10.1 -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
