From: Laurence Oberman <loberman@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>, Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Christoph Hellwig <hch@infradead.org>,
Bart Van Assche <bart.vanassche@sandisk.com>,
linux-kernel@vger.kernel.org
Subject: Re: blk-mq: don't dispatch request in blk_mq_request_direct_issue if queue is busy
Date: Thu, 18 Jan 2018 01:39:26 -0500 [thread overview]
Message-ID: <1516257566.11458.1.camel@redhat.com> (raw)
In-Reply-To: <20180118043608.GA8809@redhat.com>
On Wed, 2018-01-17 at 23:36 -0500, Mike Snitzer wrote:
> On Wed, Jan 17 2018 at 11:06pm -0500,
> Ming Lei <ming.lei@redhat.com> wrote:
>
> > If we run into blk_mq_request_direct_issue(), when queue is busy,
> > we
> > don't want to dispatch this request into hctx->dispatch_list, and
> > what we need to do is to return the queue busy info to caller, so
> > that caller can deal with it well.
> >
> > Fixes: 396eaf21ee ("blk-mq: improve DM's blk-mq IO merging via
> > blk_insert_cloned_request feedback")
> > Reported-by: Laurence Oberman <loberman@redhat.com>
> > Reviewed-by: Mike Snitzer <snitzer@redhat.com>
> > Signed-off-by: Ming Lei <ming.lei@redhat.com>
> > ---
> > block/blk-mq.c | 22 ++++++++++------------
> > 1 file changed, 10 insertions(+), 12 deletions(-)
> >
> > diff --git a/block/blk-mq.c b/block/blk-mq.c
> > index 4d4af8d712da..1af7fa70993b 100644
> > --- a/block/blk-mq.c
> > +++ b/block/blk-mq.c
> > @@ -1856,15 +1856,6 @@ static blk_status_t
> > __blk_mq_issue_directly(struct blk_mq_hw_ctx *hctx,
> > return ret;
> > }
> >
> > -static void __blk_mq_fallback_to_insert(struct request *rq,
> > - bool run_queue, bool
> > bypass_insert)
> > -{
> > - if (!bypass_insert)
> > - blk_mq_sched_insert_request(rq, false, run_queue,
> > false);
> > - else
> > - blk_mq_request_bypass_insert(rq, run_queue);
> > -}
> > -
> > static blk_status_t __blk_mq_try_issue_directly(struct
> > blk_mq_hw_ctx *hctx,
> > struct request
> > *rq,
> > blk_qc_t *cookie,
> > @@ -1873,9 +1864,16 @@ static blk_status_t
> > __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,
> > struct request_queue *q = rq->q;
> > bool run_queue = true;
> >
> > - /* RCU or SRCU read lock is needed before checking
> > quiesced flag */
> > + /*
> > + * RCU or SRCU read lock is needed before checking
> > quiesced flag.
> > + *
> > + * When queue is stopped or quiesced, ignore
> > 'bypass_insert' from
> > + * blk_mq_request_direct_issue(), and return BLK_STS_OK to
> > caller,
> > + * and avoid driver to try to dispatch again.
> > + */
> > if (blk_mq_hctx_stopped(hctx) || blk_queue_quiesced(q)) {
> > run_queue = false;
> > + bypass_insert = false;
> > goto insert;
> > }
> >
> > @@ -1892,10 +1890,10 @@ static blk_status_t
> > __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,
> >
> > return __blk_mq_issue_directly(hctx, rq, cookie);
> > insert:
> > - __blk_mq_fallback_to_insert(rq, run_queue, bypass_insert);
> > if (bypass_insert)
> > return BLK_STS_RESOURCE;
> >
> > + blk_mq_sched_insert_request(rq, false, run_queue, false);
> > return BLK_STS_OK;
> > }
>
> OK so you're just leveraging blk_mq_sched_insert_request()'s
> ability to resort to__blk_mq_insert_request() if !q->elevator.
I tested this against Mike's latest combined tree and its stable.
This fixes the list corruption issue.
Many Thanks Ming and Mike.
I will apply it to Bart's latest SRP/SRPT tree tomorrow as its very
late here but it will clearly fix the issue in Bart's tree too.
Tested-by: Laurence Oberman <loberman@redhat.com>
next prev parent reply other threads:[~2018-01-18 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 4:06 [PATCH] blk-mq: don't dispatch request in blk_mq_request_direct_issue if queue is busy Ming Lei
2018-01-18 4:36 ` Mike Snitzer
2018-01-18 6:39 ` Laurence Oberman [this message]
2018-01-18 4:39 ` [PATCH] " Jens Axboe
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=1516257566.11458.1.camel@redhat.com \
--to=loberman@redhat.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=snitzer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).