From: Mike Snitzer <snitzer@redhat.com>
To: Junichi Nomura <j-nomura@ce.jp.nec.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
device-mapper development <dm-devel@redhat.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: why is blk-mq requeue foricbly kicking stopped queues? [was: Re: dm-multipath test scripts]
Date: Mon, 22 Feb 2016 22:43:51 -0500 [thread overview]
Message-ID: <20160223034351.GA8047@redhat.com> (raw)
In-Reply-To: <56CBB72C.20309@ce.jp.nec.com>
On Mon, Feb 22 2016 at 8:34pm -0500,
Junichi Nomura <j-nomura@ce.jp.nec.com> wrote:
> On 02/23/16 00:09, Mike Snitzer wrote:
> > I should note that I applied this patch for 4.6:
> > https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.6&id=7db905b3d4294e5db4c2938fb7d0e5ba4bd798d6
> >
> > (but it was purely a fallout of code-review, and looking at the nvme's
> > use of blk_mq_requeue_request, I did't consider it to be a critical fix
> > or anything)
>
> The patch above contains following change:
>
> > +static void dm_mq_requeue_request(struct request *rq)
> > +{
> > + struct request_queue *q = rq->q;
> > + unsigned long flags;
> > +
> > + blk_mq_requeue_request(rq);
> > + spin_lock_irqsave(q->queue_lock, flags);
> > + if (!blk_queue_stopped(q))
> > + blk_mq_kick_requeue_list(q);
> > + spin_unlock_irqrestore(q->queue_lock, flags);
> > +}
>
> If you make it conditional to call blk_mq_kick_requeue_list() here,
> I think we have to call the function from start_queue(), too,
> otherwise requeued requests might stay forever in q->requeue_list.
Yes, you're right. Fixed up and pushed to rebased linux-dm.git 'dm-4.6'
branch:
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.6&id=818c5f3bef750eb5998b468f84391e4d656b97ed
next prev parent reply other threads:[~2016-02-23 3:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 5:39 dm-multipath test scripts Junichi Nomura
2015-10-07 7:31 ` Johannes Thumshirn
2015-10-08 23:10 ` Junichi Nomura
2015-11-13 10:55 ` Johannes Thumshirn
2015-11-14 16:26 ` Mike Snitzer
2016-02-18 17:17 ` Mike Snitzer
2016-02-19 0:33 ` Junichi Nomura
2016-02-19 8:37 ` Junichi Nomura
2016-02-19 19:42 ` Mike Snitzer
2016-02-20 6:12 ` Mike Snitzer
2016-02-20 9:42 ` Hannes Reinecke
2016-02-20 15:13 ` [dm-devel] " Bart Van Assche
2016-02-20 16:34 ` Mike Snitzer
2016-02-22 9:51 ` Junichi Nomura
2016-02-22 15:09 ` why is blk-mq requeue foricbly kicking stopped queues? [was: Re: dm-multipath test scripts] Mike Snitzer
2016-02-23 1:34 ` Junichi Nomura
2016-02-23 3:43 ` Mike Snitzer [this message]
2016-02-24 19:37 ` dm-multipath test scripts Mike Snitzer
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=20160223034351.GA8047@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).