From: Ming Lei <ming.lei@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@intel.com>
Subject: Re: [PATCH v2 4/8] nvme-pci: quiesce/unquiesce admin_q instead of start/stop its hw queues
Date: Wed, 5 Jul 2017 15:20:00 +0800 [thread overview]
Message-ID: <20170705071958.GD11084@ming.t460p> (raw)
In-Reply-To: <1499237591-15861-5-git-send-email-sagi@grimberg.me>
On Wed, Jul 05, 2017 at 09:53:07AM +0300, Sagi Grimberg wrote:
> unlike blk_mq_stop_hw_queues and blk_mq_start_stopped_hw_queues
> quiescing/unquiescing respects the submission path rcu grace.
>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> drivers/nvme/host/pci.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index eb729ff70e7d..df7c8a355075 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -1125,7 +1125,7 @@ static int nvme_suspend_queue(struct nvme_queue *nvmeq)
> spin_unlock_irq(&nvmeq->q_lock);
>
> if (!nvmeq->qid && nvmeq->dev->ctrl.admin_q)
> - blk_mq_stop_hw_queues(nvmeq->dev->ctrl.admin_q);
> + blk_mq_quiesce_queue(nvmeq->dev->ctrl.admin_q);
>
> pci_free_irq(to_pci_dev(nvmeq->dev->dev), vector, nvmeq);
>
> @@ -1315,7 +1315,7 @@ static void nvme_dev_remove_admin(struct nvme_dev *dev)
> * user requests may be waiting on a stopped queue. Start the
> * queue to flush these to completion.
> */
> - blk_mq_start_stopped_hw_queues(dev->ctrl.admin_q, true);
> + blk_mq_unquiesce_queue(dev->ctrl.admin_q);
> blk_cleanup_queue(dev->ctrl.admin_q);
> blk_mq_free_tag_set(&dev->admin_tagset);
> }
> @@ -1351,8 +1351,10 @@ static int nvme_alloc_admin_tags(struct nvme_dev *dev)
> dev->ctrl.admin_q = NULL;
> return -ENODEV;
> }
> - } else
> - blk_mq_start_stopped_hw_queues(dev->ctrl.admin_q, true);
> + } else {
> + blk_mq_unquiesce_queue(dev->ctrl.admin_q);
> + blk_mq_kick_requeue_list(dev->ctrl.admin_q);
> + }
Hammmm, the kick is still not needed. Actually kick requeue list
is only needed where we restart the queue. For quiesce and unquiesce,
we don't touch the STOPPED state, so needn't to kick requeue list.
--
Ming
next prev parent reply other threads:[~2017-07-05 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:53 [PATCH v2 0/8] correct quiescing in several block drivers Sagi Grimberg
2017-07-05 6:53 ` [PATCH v2 1/8] nvme-rdma: quiesce/unquiesce admin_q instead of start/stop its hw queues Sagi Grimberg
2017-07-05 7:12 ` Ming Lei
2017-07-05 7:15 ` Sagi Grimberg
2017-07-05 7:34 ` Ming Lei
2017-07-05 6:53 ` [PATCH v2 2/8] nvme-fc: " Sagi Grimberg
2017-07-05 7:16 ` Ming Lei
2017-07-05 6:53 ` [PATCH v2 3/8] nvme-loop: " Sagi Grimberg
2017-07-05 7:14 ` Ming Lei
2017-07-05 6:53 ` [PATCH v2 4/8] nvme-pci: " Sagi Grimberg
2017-07-05 7:20 ` Ming Lei [this message]
2017-07-05 6:53 ` [PATCH v2 5/8] nvme: kick requeue list when requeueing a request instead of when starting the queues Sagi Grimberg
2017-07-05 7:22 ` Ming Lei
2017-07-05 6:53 ` [PATCH v2 6/8] nbd: quiesce request queues to make sure no submissions are inflight Sagi Grimberg
2017-07-05 6:53 ` [PATCH v2 7/8] mtip32xx: " Sagi Grimberg
2017-07-05 7:28 ` Ming Lei
2017-07-05 6:53 ` [PATCH v2 8/8] virtio_blk: quiesce/unquiesce live IO when entering PM states Sagi Grimberg
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=20170705071958.GD11084@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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