All of lore.kernel.org
 help / color / mirror / Atom feed
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 5/8] nvme: kick requeue list when requeueing a request instead of when starting the queues
Date: Wed, 5 Jul 2017 15:22:22 +0800	[thread overview]
Message-ID: <20170705072221.GE11084@ming.t460p> (raw)
In-Reply-To: <1499237591-15861-6-git-send-email-sagi@grimberg.me>

On Wed, Jul 05, 2017 at 09:53:08AM +0300, Sagi Grimberg wrote:
> When we requeue a request, we can always insert the request
> back to the scheduler instead of doing it when restarting
> the queues and kicking the requeue work, so get rid of
> the requeue kick in nvme (core and drivers).
> 
> Also, now there is no need start hw queues in nvme_kill_queues
> We don't stop the hw queues anymore, so no need to
> start them.
> 
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
>  drivers/nvme/host/core.c | 19 ++-----------------
>  drivers/nvme/host/fc.c   |  4 +---
>  drivers/nvme/host/pci.c  |  1 -
>  drivers/nvme/host/rdma.c |  1 -
>  4 files changed, 3 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index d70df1d0072d..48cafaa6fbc5 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -131,7 +131,7 @@ void nvme_complete_rq(struct request *req)
>  {
>  	if (unlikely(nvme_req(req)->status && nvme_req_needs_retry(req))) {
>  		nvme_req(req)->retries++;
> -		blk_mq_requeue_request(req, !blk_mq_queue_stopped(req->q));
> +		blk_mq_requeue_request(req, true);
>  		return;
>  	}

This change is correct.

-- 
Ming

WARNING: multiple messages have this Message-ID (diff)
From: ming.lei@redhat.com (Ming Lei)
Subject: [PATCH v2 5/8] nvme: kick requeue list when requeueing a request instead of when starting the queues
Date: Wed, 5 Jul 2017 15:22:22 +0800	[thread overview]
Message-ID: <20170705072221.GE11084@ming.t460p> (raw)
In-Reply-To: <1499237591-15861-6-git-send-email-sagi@grimberg.me>

On Wed, Jul 05, 2017@09:53:08AM +0300, Sagi Grimberg wrote:
> When we requeue a request, we can always insert the request
> back to the scheduler instead of doing it when restarting
> the queues and kicking the requeue work, so get rid of
> the requeue kick in nvme (core and drivers).
> 
> Also, now there is no need start hw queues in nvme_kill_queues
> We don't stop the hw queues anymore, so no need to
> start them.
> 
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> ---
>  drivers/nvme/host/core.c | 19 ++-----------------
>  drivers/nvme/host/fc.c   |  4 +---
>  drivers/nvme/host/pci.c  |  1 -
>  drivers/nvme/host/rdma.c |  1 -
>  4 files changed, 3 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index d70df1d0072d..48cafaa6fbc5 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -131,7 +131,7 @@ void nvme_complete_rq(struct request *req)
>  {
>  	if (unlikely(nvme_req(req)->status && nvme_req_needs_retry(req))) {
>  		nvme_req(req)->retries++;
> -		blk_mq_requeue_request(req, !blk_mq_queue_stopped(req->q));
> +		blk_mq_requeue_request(req, true);
>  		return;
>  	}

This change is correct.

-- 
Ming

  reply	other threads:[~2017-07-05  7:22 UTC|newest]

Thread overview: 34+ 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 ` 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  6:53   ` Sagi Grimberg
2017-07-05  7:12   ` Ming Lei
2017-07-05  7:12     ` Ming Lei
2017-07-05  7:15     ` Sagi Grimberg
2017-07-05  7:15       ` Sagi Grimberg
2017-07-05  7:34       ` Ming Lei
2017-07-05  7:34         ` Ming Lei
2017-07-05  6:53 ` [PATCH v2 2/8] nvme-fc: " Sagi Grimberg
2017-07-05  6:53   ` Sagi Grimberg
2017-07-05  7:16   ` Ming Lei
2017-07-05  7:16     ` Ming Lei
2017-07-05  6:53 ` [PATCH v2 3/8] nvme-loop: " Sagi Grimberg
2017-07-05  6:53   ` Sagi Grimberg
2017-07-05  7:14   ` Ming Lei
2017-07-05  7:14     ` Ming Lei
2017-07-05  6:53 ` [PATCH v2 4/8] nvme-pci: " Sagi Grimberg
2017-07-05  6:53   ` Sagi Grimberg
2017-07-05  7:20   ` Ming Lei
2017-07-05  7:20     ` Ming Lei
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  6:53   ` Sagi Grimberg
2017-07-05  7:22   ` Ming Lei [this message]
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   ` Sagi Grimberg
2017-07-05  6:53 ` [PATCH v2 7/8] mtip32xx: " Sagi Grimberg
2017-07-05  6:53   ` Sagi Grimberg
2017-07-05  7:28   ` Ming Lei
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
2017-07-05  6:53   ` 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=20170705072221.GE11084@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 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.