linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Smart <jsmart2021@gmail.com>
To: Jianchao Wang <jianchao.w.wang@oracle.com>, axboe@kernel.dk
Cc: hch@lst.de, jthumshirn@suse.de, hare@suse.de,
	josef@toxicpanda.com, bvanassche@acm.org, sagi@grimberg.me,
	keith.busch@intel.com, linux-block@vger.kernel.org,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/8] nvme: use blk_mq_queue_tag_busy_iter
Date: Fri, 15 Mar 2019 09:33:39 -0700	[thread overview]
Message-ID: <62de99e8-0d8d-910a-bfdc-649f734b152c@gmail.com> (raw)
In-Reply-To: <1552640264-26101-8-git-send-email-jianchao.w.wang@oracle.com>

On 3/15/2019 1:57 AM, Jianchao Wang wrote:
> blk_mq_tagset_busy_iter is not safe that it could get stale request
> in tags->rqs[]. Use blk_mq_queue_tag_busy_iter here. A new helper
> interface nvme_iterate_inflight_rqs is introduced to iterate
> all of the ns under a ctrl.
> 
> Signed-off-by: Jianchao Wang <jianchao.w.wang@oracle.com>
> ---
>   drivers/nvme/host/core.c   | 12 ++++++++++++
>   drivers/nvme/host/fc.c     | 12 ++++++------
>   drivers/nvme/host/nvme.h   |  2 ++
>   drivers/nvme/host/pci.c    |  5 +++--
>   drivers/nvme/host/rdma.c   |  6 +++---
>   drivers/nvme/host/tcp.c    |  5 +++--
>   drivers/nvme/target/loop.c |  6 +++---
>   7 files changed, 32 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index 6a9dd68..5760fad 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -3816,6 +3816,18 @@ void nvme_start_queues(struct nvme_ctrl *ctrl)
>   }
>   EXPORT_SYMBOL_GPL(nvme_start_queues);
>   
> +void nvme_iterate_inflight_rqs(struct nvme_ctrl *ctrl,
> +		busy_iter_fn *fn, void *data)
> +{
> +	struct nvme_ns *ns;
> +
> +	down_read(&ctrl->namespaces_rwsem);
> +	list_for_each_entry(ns, &ctrl->namespaces, list)
> +		blk_mq_queue_tag_busy_iter(ns->queue, fn, data, true);
> +	up_read(&ctrl->namespaces_rwsem);
> +}
> +EXPORT_SYMBOL_GPL(nvme_iterate_inflight_rqs);

Hmm... so this aborts ios for namespaces. How about ios that aren't for 
a namespace but rather for the controller itself.  For example, anything 
on the admin queue ?   Rather critical for those ios be terminated as well.

-- james


  reply	other threads:[~2019-03-15 16:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  8:57 [PATCH 0/8]: blk-mq: use static_rqs to iterate busy tags Jianchao Wang
2019-03-15  8:57 ` [PATCH 1/8] blk-mq: get rid of the synchronize_rcu in __blk_mq_update_nr_hw_queues Jianchao Wang
2019-03-17  6:14   ` Ming Lei
2019-03-15  8:57 ` [PATCH 2/8] blk-mq: change the method of iterating busy tags of a request_queue Jianchao Wang
2019-03-15 16:16   ` Keith Busch
2019-03-17  6:50     ` Ming Lei
2019-03-18 15:53       ` Keith Busch
2019-03-18  1:49     ` jianchao.wang
2019-03-20 18:52   ` Sagi Grimberg
2019-03-21  1:33     ` jianchao.wang
2019-03-15  8:57 ` [PATCH 3/8] blk-mq: use blk_mq_queue_tag_busy_iter in debugfs Jianchao Wang
2019-03-15  8:57 ` [PATCH 4/8] mtip32xx: use blk_mq_queue_tag_busy_iter Jianchao Wang
2019-03-15  8:57 ` [PATCH 5/8] nbd: " Jianchao Wang
2019-03-18 17:16   ` Bart Van Assche
2019-03-19  2:04     ` jianchao.wang
2019-03-15  8:57 ` [PATCH 6/8] skd: " Jianchao Wang
2019-03-18 17:20   ` Bart Van Assche
2019-03-19  1:54     ` jianchao.wang
2019-03-15  8:57 ` [PATCH 7/8] nvme: " Jianchao Wang
2019-03-15 16:33   ` James Smart [this message]
2019-03-15 16:39     ` James Smart
2019-03-15 16:49       ` Hannes Reinecke
2019-03-18  7:00     ` jianchao.wang
2019-03-15  8:57 ` [PATCH 8/8] blk-mq: remove blk_mq_tagset_busy_iter Jianchao Wang
2019-03-15  9:20 ` [PATCH 0/8]: blk-mq: use static_rqs to iterate busy tags Christoph Hellwig
2019-03-15  9:44   ` jianchao.wang
2019-03-15 16:19     ` Bart Van Assche
2019-03-18  2:47       ` jianchao.wang
2019-03-15 13:30   ` Josef Bacik
2019-03-18 17:28 ` Bart Van Assche
2019-03-19  1:25   ` jianchao.wang
2019-03-19 15:10     ` Bart Van Assche
2019-03-19 15:25       ` Keith Busch
2019-03-20 18:38         ` 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=62de99e8-0d8d-910a-bfdc-649f734b152c@gmail.com \
    --to=jsmart2021@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jianchao.w.wang@oracle.com \
    --cc=josef@toxicpanda.com \
    --cc=jthumshirn@suse.de \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).