From: Ming Lin <mlin@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
keith.busch@intel.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/8] blk-mq: add blk_mq_alloc_request_hctx
Date: Tue, 07 Jun 2016 22:20:36 -0700 [thread overview]
Message-ID: <1465363236.10841.13.camel@kernel.org> (raw)
In-Reply-To: <5757A3D2.1030003@kernel.dk>
On Tue, 2016-06-07 at 22:49 -0600, Jens Axboe wrote:
> On 06/06/2016 03:21 PM, Christoph Hellwig wrote:
> > From: Ming Lin <ming.l@ssi.samsung.com>
> >
> > For some protocols like NVMe over Fabrics we need to be able to
> > send
> > initialization commands to a specific queue.
> >
> > Based on an earlier patch from Christoph Hellwig <hch@lst.de>.
> >
> > Signed-off-by: Ming Lin <ming.l@ssi.samsung.com>
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> > block/blk-mq.c | 33 +++++++++++++++++++++++++++++++++
> > include/linux/blk-mq.h | 2 ++
> > 2 files changed, 35 insertions(+)
> >
> > diff --git a/block/blk-mq.c b/block/blk-mq.c
> > index 29cbc1b..7bb45ed 100644
> > --- a/block/blk-mq.c
> > +++ b/block/blk-mq.c
> > @@ -266,6 +266,39 @@ struct request *blk_mq_alloc_request(struct
> > request_queue *q, int rw,
> > }
> > EXPORT_SYMBOL(blk_mq_alloc_request);
> >
> > +struct request *blk_mq_alloc_request_hctx(struct request_queue *q,
> > int rw,
> > + unsigned int flags, unsigned int hctx_idx)
> > +{
> > + struct blk_mq_hw_ctx *hctx;
> > + struct blk_mq_ctx *ctx;
> > + struct request *rq;
> > + struct blk_mq_alloc_data alloc_data;
> > + int ret;
> > +
> > + ret = blk_queue_enter(q, flags & BLK_MQ_REQ_NOWAIT);
> > + if (ret)
> > + return ERR_PTR(ret);
> > +
> > + hctx = q->queue_hw_ctx[hctx_idx];
> > + ctx = __blk_mq_get_ctx(q, cpumask_first(hctx->cpumask));
> > +
> > + blk_mq_set_alloc_data(&alloc_data, q, flags, ctx, hctx);
> > +
> > + rq = __blk_mq_alloc_request(&alloc_data, rw);
> > + if (!rq && !(flags & BLK_MQ_REQ_NOWAIT)) {
> > + __blk_mq_run_hw_queue(hctx);
> > +
> > + rq = __blk_mq_alloc_request(&alloc_data, rw);
> > + }
>
> Why are we duplicating this code here? If NOWAIT isn't set, then
> we'll
> always return a request. bt_get() will run the queue for us, if it
> needs
> to. blk_mq_alloc_request() does this too, and I'm guessing that code
> was
> just copied. I'll fix that up. Looks like this should just be:
>
> rq = __blk_mq_alloc_request(&alloc_data, rw);
> if (rq)
> return rq;
>
> blk_queue_exit(q);
> return ERR_PTR(-EWOULDBLOCK);
>
> for this case.
Yes,
But the bt_get() reminds me that this patch actually has a problem.
blk_mq_alloc_request_hctx() ->
__blk_mq_alloc_request() ->
blk_mq_get_tag() ->
__blk_mq_get_tag() ->
bt_get() ->
blk_mq_put_ctx(data->ctx);
Here are blk_mq_get_ctx() and blk_mq_put_ctx().
static inline struct blk_mq_ctx *blk_mq_get_ctx(struct request_queue *q)
{
return __blk_mq_get_ctx(q, get_cpu());
}
static inline void blk_mq_put_ctx(struct blk_mq_ctx *ctx)
{
put_cpu();
}
blk_mq_alloc_request_hctx() calls __blk_mq_get_ctx() instead
of blk_mq_get_ctx(). Then reason is the "hctx" could belong to other
cpu. So blk_mq_get_ctx() doesn't work.
But then above put_cpu() in blk_mq_put_ctx() will trigger a WARNING
because we didn't do get_cpu() in blk_mq_alloc_request_hctx()
next prev parent reply other threads:[~2016-06-08 5:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 21:21 generic NVMe over Fabrics library support Christoph Hellwig
2016-06-06 21:21 ` [PATCH 1/8] blk-mq: add blk_mq_alloc_request_hctx Christoph Hellwig
2016-06-07 14:57 ` Keith Busch
2016-06-07 15:27 ` Ming Lin
2016-06-07 23:21 ` Ming Lin
2016-06-08 4:49 ` Jens Axboe
2016-06-08 5:20 ` Ming Lin [this message]
2016-06-08 11:56 ` Christoph Hellwig
2016-06-08 11:54 ` Christoph Hellwig
2016-06-06 21:21 ` [PATCH 2/8] nvme: allow transitioning from NEW to LIVE state Christoph Hellwig
2016-06-06 21:21 ` [PATCH 3/8] nvme: Modify and export sync command submission for fabrics Christoph Hellwig
2016-06-06 21:21 ` [PATCH 4/8] nvme: add fabrics sysfs attributes Christoph Hellwig
2016-06-07 8:52 ` Johannes Thumshirn
2016-06-07 10:51 ` Christoph Hellwig
2016-06-07 15:21 ` Christoph Hellwig
2016-06-06 21:21 ` [PATCH 5/8] nvme.h: add NVMe over Fabrics definitions Christoph Hellwig
2016-06-06 21:21 ` [PATCH 6/8] nvme-fabrics: add a generic NVMe over Fabrics library Christoph Hellwig
2016-06-06 21:21 ` [PATCH 7/8] nvme.h: Add keep-alive opcode and identify controller attribute Christoph Hellwig
2016-06-06 21:21 ` [PATCH 8/8] nvme: add keep-alive support Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2016-06-13 14:45 generic NVMe over Fabrics library support V2 Christoph Hellwig
2016-06-13 14:45 ` [PATCH 1/8] blk-mq: add blk_mq_alloc_request_hctx 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=1465363236.10841.13.camel@kernel.org \
--to=mlin@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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).