All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "jianchao.wang" <jianchao.w.wang@oracle.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Ming Lei <ming.lei@redhat.com>
Subject: Re: WARNING: CPU: 2 PID: 207 at drivers/nvme/host/core.c:527 nvme_setup_cmd+0x3d3
Date: Thu, 1 Feb 2018 11:01:20 -0700	[thread overview]
Message-ID: <20180201180120.GA24417@localhost.localdomain> (raw)
In-Reply-To: <576ba7dc-78cf-b5d2-d1de-446d1f4b2732@kernel.dk>

On Thu, Feb 01, 2018 at 08:26:11AM -0700, Jens Axboe wrote:
> On 1/31/18 9:56 PM, Keith Busch wrote:
> 
> > diff --git a/block/blk-merge.c b/block/blk-merge.c
> > index 8452fc7164cc..01671e1373ff 100644
> > --- a/block/blk-merge.c
> > +++ b/block/blk-merge.c
> > @@ -550,6 +550,28 @@ static bool req_no_special_merge(struct request *req)
> >  	return !q->mq_ops && req->special;
> >  }
> >  
> > +static bool req_attempt_discard_merge(struct request_queue *q, struct request *req,
> > +		struct request *next)
> > +{
> > +	unsigned short segments = blk_rq_nr_discard_segments(req);
> > +
> > +	if (segments >= queue_max_discard_segments(q))
> > +		goto no_merge;
> > +	if (blk_rq_sectors(req) + bio_sectors(next->bio) >
> > +	    blk_rq_get_max_sectors(req, blk_rq_pos(req)))
> > +		goto no_merge;
> > +
> > +	req->biotail->bi_next = next->bio;
> > +	req->biotail = next->biotail;
> > +	req->nr_phys_segments = segments + blk_rq_nr_discard_segments(next);
> > +	next->bio = NULL;
> > +	return true;
> > +
> > +no_merge:
> > +	req_set_nomerge(q, req);
> > +	return false;
> > +}
> > +
> >  static int ll_merge_requests_fn(struct request_queue *q, struct request *req,
> >  				struct request *next)
> >  {
> > @@ -679,6 +701,15 @@ static struct request *attempt_merge(struct request_queue *q,
> >  	if (req->write_hint != next->write_hint)
> >  		return NULL;
> >  
> > +	/*
> > +	 * Discards are ... special.
> > +	 */
> > +	if (req_op(req) == REQ_OP_DISCARD) {
> > +		if (req_attempt_discard_merge(q, req, next))
> > +			return next;
> > +		return NULL;
> > +	}
> > +
> >  	/*
> >  	 * If we are allowed to merge, then append bio list
> >  	 * from next to rq and release next. merge_requests_fn
> 
> This looks fine to me, the bio-to-request merge path already looks correct.
> Care to send a properly formatted patch?

Sending the patch now. It's a little different from the above so that it
doesn't need to duplicate some of the merging accounting.

Full disclosure, I have not found a way to trigger this merge. I'm just
running 'fio' with trim, randtrim, and trimwrite on device with
mq-deadline for the past hour, and haven't seen a merge happen yet.

WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@intel.com (Keith Busch)
Subject: WARNING: CPU: 2 PID: 207 at drivers/nvme/host/core.c:527 nvme_setup_cmd+0x3d3
Date: Thu, 1 Feb 2018 11:01:20 -0700	[thread overview]
Message-ID: <20180201180120.GA24417@localhost.localdomain> (raw)
In-Reply-To: <576ba7dc-78cf-b5d2-d1de-446d1f4b2732@kernel.dk>

On Thu, Feb 01, 2018@08:26:11AM -0700, Jens Axboe wrote:
> On 1/31/18 9:56 PM, Keith Busch wrote:
> 
> > diff --git a/block/blk-merge.c b/block/blk-merge.c
> > index 8452fc7164cc..01671e1373ff 100644
> > --- a/block/blk-merge.c
> > +++ b/block/blk-merge.c
> > @@ -550,6 +550,28 @@ static bool req_no_special_merge(struct request *req)
> >  	return !q->mq_ops && req->special;
> >  }
> >  
> > +static bool req_attempt_discard_merge(struct request_queue *q, struct request *req,
> > +		struct request *next)
> > +{
> > +	unsigned short segments = blk_rq_nr_discard_segments(req);
> > +
> > +	if (segments >= queue_max_discard_segments(q))
> > +		goto no_merge;
> > +	if (blk_rq_sectors(req) + bio_sectors(next->bio) >
> > +	    blk_rq_get_max_sectors(req, blk_rq_pos(req)))
> > +		goto no_merge;
> > +
> > +	req->biotail->bi_next = next->bio;
> > +	req->biotail = next->biotail;
> > +	req->nr_phys_segments = segments + blk_rq_nr_discard_segments(next);
> > +	next->bio = NULL;
> > +	return true;
> > +
> > +no_merge:
> > +	req_set_nomerge(q, req);
> > +	return false;
> > +}
> > +
> >  static int ll_merge_requests_fn(struct request_queue *q, struct request *req,
> >  				struct request *next)
> >  {
> > @@ -679,6 +701,15 @@ static struct request *attempt_merge(struct request_queue *q,
> >  	if (req->write_hint != next->write_hint)
> >  		return NULL;
> >  
> > +	/*
> > +	 * Discards are ... special.
> > +	 */
> > +	if (req_op(req) == REQ_OP_DISCARD) {
> > +		if (req_attempt_discard_merge(q, req, next))
> > +			return next;
> > +		return NULL;
> > +	}
> > +
> >  	/*
> >  	 * If we are allowed to merge, then append bio list
> >  	 * from next to rq and release next. merge_requests_fn
> 
> This looks fine to me, the bio-to-request merge path already looks correct.
> Care to send a properly formatted patch?

Sending the patch now. It's a little different from the above so that it
doesn't need to duplicate some of the merging accounting.

Full disclosure, I have not found a way to trigger this merge. I'm just
running 'fio' with trim, randtrim, and trimwrite on device with
mq-deadline for the past hour, and haven't seen a merge happen yet.

  parent reply	other threads:[~2018-02-01 18:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 15:41 WARNING: CPU: 2 PID: 207 at drivers/nvme/host/core.c:527 nvme_setup_cmd+0x3d3 Jens Axboe
2018-01-30 15:41 ` Jens Axboe
2018-01-30 15:57 ` Jens Axboe
2018-01-30 15:57   ` Jens Axboe
2018-01-30 20:30   ` Keith Busch
2018-01-30 20:30     ` Keith Busch
2018-01-30 20:32     ` Jens Axboe
2018-01-30 20:32       ` Jens Axboe
2018-01-30 20:49       ` Keith Busch
2018-01-30 20:49         ` Keith Busch
2018-01-30 20:55         ` Jens Axboe
2018-01-30 20:55           ` Jens Axboe
2018-01-31  4:25   ` jianchao.wang
2018-01-31  4:25     ` jianchao.wang
2018-01-31 15:29     ` Jens Axboe
2018-01-31 15:29       ` Jens Axboe
2018-01-31 23:33       ` Keith Busch
2018-01-31 23:33         ` Keith Busch
2018-02-01  3:03         ` Jens Axboe
2018-02-01  3:03           ` Jens Axboe
2018-02-01  3:03       ` jianchao.wang
2018-02-01  3:03         ` jianchao.wang
2018-02-01  3:07         ` Jens Axboe
2018-02-01  3:07           ` Jens Axboe
2018-02-01  3:33           ` jianchao.wang
2018-02-01  3:33             ` jianchao.wang
2018-02-01  3:35             ` Jens Axboe
2018-02-01  3:35               ` Jens Axboe
2018-02-01  4:56           ` Keith Busch
2018-02-01  4:56             ` Keith Busch
2018-02-01 15:26             ` Jens Axboe
2018-02-01 15:26               ` Jens Axboe
2018-02-01 17:58               ` Jens Axboe
2018-02-01 17:58                 ` Jens Axboe
2018-02-01 18:12                 ` Keith Busch
2018-02-01 18:12                   ` Keith Busch
2018-02-01 19:52                 ` Keith Busch
2018-02-01 19:52                   ` Keith Busch
2018-02-01 20:55                   ` Jens Axboe
2018-02-01 20:55                     ` Jens Axboe
2018-02-01 18:01               ` Keith Busch [this message]
2018-02-01 18:01                 ` Keith Busch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180201180120.GA24417@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jianchao.w.wang@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ming.lei@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.