From: Jeff Moyer <jmoyer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: keith.busch@intel.com, axboe@kernel.dk,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
sagi@lightbits.io, ming.l@ssi.samsung.com
Subject: Re: [PATCH 01/11] Revert "blk-mq: add blk_mq_alloc_request_hctx"
Date: Wed, 08 Jun 2016 09:58:38 -0400 [thread overview]
Message-ID: <x49mvmv235d.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1465389066-19119-2-git-send-email-hch@lst.de> (Christoph Hellwig's message of "Wed, 8 Jun 2016 14:30:56 +0200")
Christoph Hellwig <hch@lst.de> writes:
> Just for book keeping. The next patch brings it back with some changes.
That's a strange thing to do, and breaks bisectability. Why not just
update the function?
-Jeff
>
> This reverts commit 98878e0f0b80520575b31147f7cff28e28d9a725.
> ---
> block/blk-mq.c | 33 ---------------------------------
> include/linux/blk-mq.h | 2 --
> 2 files changed, 35 deletions(-)
>
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 049356d..13f4603 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -267,39 +267,6 @@ 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);
> - }
> - if (!rq) {
> - blk_queue_exit(q);
> - return ERR_PTR(-EWOULDBLOCK);
> - }
> -
> - return rq;
> -}
> -EXPORT_SYMBOL(blk_mq_alloc_request_hctx);
> -
> static void __blk_mq_free_request(struct blk_mq_hw_ctx *hctx,
> struct blk_mq_ctx *ctx, struct request *rq)
> {
> diff --git a/include/linux/blk-mq.h b/include/linux/blk-mq.h
> index 9a5d581..faa7d5c2 100644
> --- a/include/linux/blk-mq.h
> +++ b/include/linux/blk-mq.h
> @@ -198,8 +198,6 @@ enum {
>
> struct request *blk_mq_alloc_request(struct request_queue *q, int rw,
> unsigned int flags);
> -struct request *blk_mq_alloc_request_hctx(struct request_queue *q, int rw,
> - unsigned int flags, unsigned int hctx_idx);
> struct request *blk_mq_tag_to_rq(struct blk_mq_tags *tags, unsigned int tag);
> struct cpumask *blk_mq_tags_cpumask(struct blk_mq_tags *tags);
next prev parent reply other threads:[~2016-06-08 13:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 12:30 NVMe over Fabrics: updates for req_op changes and misc fixes Christoph Hellwig
2016-06-08 12:30 ` [PATCH 01/11] Revert "blk-mq: add blk_mq_alloc_request_hctx" Christoph Hellwig
2016-06-08 13:58 ` Jeff Moyer [this message]
2016-06-08 14:10 ` Christoph Hellwig
2016-06-08 14:13 ` Jeff Moyer
2016-06-08 12:30 ` [PATCH 02/11] blk-mq: add blk_mq_alloc_request_hctx Christoph Hellwig
2016-06-08 13:43 ` Sagi Grimberg
2016-06-08 12:30 ` [PATCH 03/11] nvme_rdma: update for req_op changes Christoph Hellwig
2016-06-08 13:44 ` Sagi Grimberg
2016-06-08 22:03 ` Ming Lin
2016-06-08 12:30 ` [PATCH 04/11] nvmet: " Christoph Hellwig
2016-06-08 13:44 ` Sagi Grimberg
2016-06-14 14:27 ` Christoph Hellwig
2016-06-08 12:31 ` [PATCH 05/11] nvme-loop: set SGL flag on AER Christoph Hellwig
2016-06-08 12:31 ` [PATCH 06/11] nvme-rdma: " Christoph Hellwig
2016-06-08 12:31 ` [PATCH 07/11] nvmet: fix 64-bit division in nvmet_set_features Christoph Hellwig
2016-06-08 13:53 ` Sagi Grimberg
2016-06-08 12:31 ` [PATCH 08/11] nvmet: fix eno.cocci warnings Christoph Hellwig
2016-06-08 22:09 ` Ming Lin
2016-06-08 12:31 ` [PATCH 09/11] nvmet-rdma: check for a valid adrfam Christoph Hellwig
2016-06-08 12:31 ` [PATCH 10/11] nvme: keep alive should use any queue Christoph Hellwig
2016-06-08 13:54 ` Sagi Grimberg
2016-06-08 12:31 ` [PATCH 11/11] nvme-fabrics: pass non-blocking flag to connect request allocation Christoph Hellwig
2016-06-08 13:55 ` Sagi Grimberg
2016-06-08 14:09 ` Christoph Hellwig
2016-06-08 22:21 ` NVMe over Fabrics: updates for req_op changes and misc fixes Ming Lin
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=x49mvmv235d.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@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=ming.l@ssi.samsung.com \
--cc=sagi@lightbits.io \
/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).