On Tue, Apr 26, 2016 at 7:52 AM, Shaohua Li <shli@xxxxxx> wrote: > blk_queue_split marks bio unmergeable, which makes sense for normal bio. > But if dispatching the bio to underlayer disk, the blk_queue_split > checks are invalid, hence it's possible the bio becomes mergeable. If the bio from md is splitted and marked as NOMERGE, it means some queue limits are reached. So looks the raid's queue limit is set as not big enough, could your find which limit causes the splitting and nomerge? > > In the reported bug, this bug causes trim against raid0 performance slash > https://bugzilla.kernel.org/show_bug.cgi?id=117051 > > Reported-by: Park Ju Hyung <qkrwngud825@xxxxxxxxx> > Fixes: 6ac45aeb6bca(block: avoid to merge splitted bio) > Cc: stable@xxxxxxxxxxxxxxx (v4.3+) > Cc: Ming Lei <ming.lei@xxxxxxxxxxxxx> > Cc: Jens Axboe <axboe@xxxxxx> > Cc: Neil Brown <neilb@xxxxxxx> > Signed-off-by: Shaohua Li <shli@xxxxxx> > --- > drivers/md/md.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/md/md.c b/drivers/md/md.c > index 194580f..14d3b37 100644 > --- a/drivers/md/md.c > +++ b/drivers/md/md.c > @@ -284,6 +284,8 @@ static blk_qc_t md_make_request(struct request_queue *q, struct bio *bio) > * go away inside make_request > */ > sectors = bio_sectors(bio); > + /* bio could be mergeable after passing to underlayer */ > + bio->bi_rw &= ~REQ_NOMERGE; IMO it isn't a good fix, eigher we need to set a correct queue limit, or we simply don't set nomerge for all stackable block device. But I prefer to the former a bit. Thanks, > mddev->pers->make_request(mddev, bio); > > cpu = part_stat_lock(); > -- > 2.8.0.rc2 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-block" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
