All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <keith.busch@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
	Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 9/9] nvme: implement multipath access to nvme subsystems
Date: Sun, 24 Sep 2017 16:48:31 +0200	[thread overview]
Message-ID: <20170924144831.GC13681@lst.de> (raw)
In-Reply-To: <20170922150915.GA1294@localhost.localdomain>

On Fri, Sep 22, 2017 at 11:09:16AM -0400, Keith Busch wrote:
> On Mon, Sep 18, 2017 at 04:14:53PM -0700, Christoph Hellwig wrote:
> > +static void nvme_failover_req(struct request *req)
> > +{
> > +	struct nvme_ns *ns = req->q->queuedata;
> > +	unsigned long flags;
> > +
> > +	spin_lock_irqsave(&ns->head->requeue_lock, flags);
> > +	blk_steal_bios(&ns->head->requeue_list, req);
> > +	spin_unlock_irqrestore(&ns->head->requeue_lock, flags);
> > +
> > +	nvme_reset_ctrl(ns->ctrl);
> > +	kblockd_schedule_work(&ns->head->requeue_work);
> > +}
> 
> Need to call blk_mq_free_req after stealing all its bios to prevent
> leaking that entered request.

I think this should be a blk_mq_end_request actually.  The difference
is that blk_mq_end_request will get the I/O accounting right, and
treats the case of having and ->end_io handler correctly as well.

WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 9/9] nvme: implement multipath access to nvme subsystems
Date: Sun, 24 Sep 2017 16:48:31 +0200	[thread overview]
Message-ID: <20170924144831.GC13681@lst.de> (raw)
In-Reply-To: <20170922150915.GA1294@localhost.localdomain>

On Fri, Sep 22, 2017@11:09:16AM -0400, Keith Busch wrote:
> On Mon, Sep 18, 2017@04:14:53PM -0700, Christoph Hellwig wrote:
> > +static void nvme_failover_req(struct request *req)
> > +{
> > +	struct nvme_ns *ns = req->q->queuedata;
> > +	unsigned long flags;
> > +
> > +	spin_lock_irqsave(&ns->head->requeue_lock, flags);
> > +	blk_steal_bios(&ns->head->requeue_list, req);
> > +	spin_unlock_irqrestore(&ns->head->requeue_lock, flags);
> > +
> > +	nvme_reset_ctrl(ns->ctrl);
> > +	kblockd_schedule_work(&ns->head->requeue_work);
> > +}
> 
> Need to call blk_mq_free_req after stealing all its bios to prevent
> leaking that entered request.

I think this should be a blk_mq_end_request actually.  The difference
is that blk_mq_end_request will get the I/O accounting right, and
treats the case of having and ->end_io handler correctly as well.

  reply	other threads:[~2017-09-24 14:48 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 23:14 nvme multipath support V2 Christoph Hellwig
2017-09-18 23:14 ` Christoph Hellwig
2017-09-18 23:14 ` [PATCH 1/9] nvme: allow timed-out ios to retry Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-18 23:14 ` [PATCH 2/9] block: move REQ_NOWAIT Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-18 23:14 ` [PATCH 3/9] block: add REQ_DRV bit Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-18 23:14 ` [PATCH 4/9] block: provide a direct_make_request helper Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-18 23:14 ` [PATCH 5/9] block: add a blk_steal_bios helper Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-18 23:14 ` [PATCH 6/9] nvme: track subsystems Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-21 22:52   ` Keith Busch
2017-09-21 22:52     ` Keith Busch
2017-09-18 23:14 ` [PATCH 7/9] nvme: introduce a nvme_ns_ids structure Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-20  8:27   ` Johannes Thumshirn
2017-09-20  8:27     ` Johannes Thumshirn
2017-09-18 23:14 ` [PATCH 8/9] nvme: track shared namespaces Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-20  8:36   ` Johannes Thumshirn
2017-09-20  8:36     ` Johannes Thumshirn
2017-09-20 14:54     ` Christoph Hellwig
2017-09-20 14:54       ` Christoph Hellwig
2017-09-21  5:22       ` Johannes Thumshirn
2017-09-21  5:22         ` Johannes Thumshirn
2017-09-21 14:37         ` Christoph Hellwig
2017-09-21 14:37           ` Christoph Hellwig
2017-09-21 15:16           ` Keith Busch
2017-09-21 15:16             ` Keith Busch
2017-09-24 15:25             ` Christoph Hellwig
2017-09-24 15:25               ` Christoph Hellwig
2017-09-18 23:14 ` [PATCH 9/9] nvme: implement multipath access to nvme subsystems Christoph Hellwig
2017-09-18 23:14   ` Christoph Hellwig
2017-09-20  0:18   ` Tony Yang
2017-09-20  0:18     ` Tony Yang
2017-09-20  8:15     ` Johannes Thumshirn
2017-09-20  8:15       ` Johannes Thumshirn
2017-09-20  9:42   ` Johannes Thumshirn
2017-09-20  9:42     ` Johannes Thumshirn
2017-09-20 22:58   ` Keith Busch
2017-09-20 22:58     ` Keith Busch
2017-09-20 23:52     ` Christoph Hellwig
2017-09-20 23:52       ` Christoph Hellwig
2017-09-21 21:12       ` Keith Busch
2017-09-21 21:12         ` Keith Busch
2017-09-24 14:42         ` Christoph Hellwig
2017-09-24 14:42           ` Christoph Hellwig
2017-09-22 15:09   ` Keith Busch
2017-09-22 15:09     ` Keith Busch
2017-09-24 14:48     ` Christoph Hellwig [this message]
2017-09-24 14:48       ` Christoph Hellwig
2017-09-20 11:09 ` nvme multipath support V2 Johannes Thumshirn
2017-09-20 11:09   ` Johannes Thumshirn
2017-09-20 14:55   ` Christoph Hellwig
2017-09-20 14:55     ` Christoph Hellwig
2017-09-21  5:23     ` Johannes Thumshirn
2017-09-21  5:23       ` Johannes Thumshirn
2017-09-21 14:50       ` Christoph Hellwig
2017-09-21 14:50         ` Christoph Hellwig
2017-09-22  0:21         ` Tony Yang
2017-09-22  0:21           ` Tony Yang
2017-09-24 14:41           ` Christoph Hellwig
2017-09-24 14:41             ` Christoph Hellwig

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=20170924144831.GC13681@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --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.