From: Sagi Grimberg <sagi@grimberg.me>
To: Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, axboe@kernel.dk,
linux-nvme@lists.infradead.org, hch@lst.de
Cc: Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 2/3] nvme: add polling options for loop target
Date: Wed, 22 Mar 2023 09:44:54 +0200 [thread overview]
Message-ID: <6c5bddde-7a9e-c7be-4302-ce0334708914@grimberg.me> (raw)
In-Reply-To: <20230322002350.4038048-3-kbusch@meta.com>
On 3/22/23 02:23, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> This is for mostly for testing purposes.
>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
> drivers/nvme/target/loop.c | 63 +++++++++++++++++++++++++++++++++++---
> 1 file changed, 58 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/nvme/target/loop.c b/drivers/nvme/target/loop.c
> index f2d24b2d992f8..0587ead60b09e 100644
> --- a/drivers/nvme/target/loop.c
> +++ b/drivers/nvme/target/loop.c
> @@ -22,6 +22,7 @@ struct nvme_loop_iod {
> struct nvmet_req req;
> struct nvme_loop_queue *queue;
> struct work_struct work;
> + struct work_struct poll;
> struct sg_table sg_table;
> struct scatterlist first_sgl[];
> };
> @@ -37,6 +38,7 @@ struct nvme_loop_ctrl {
> struct nvme_ctrl ctrl;
>
> struct nvmet_port *port;
> + u32 io_queues[HCTX_MAX_TYPES];
> };
>
> static inline struct nvme_loop_ctrl *to_loop_ctrl(struct nvme_ctrl *ctrl)
> @@ -76,7 +78,11 @@ static void nvme_loop_complete_rq(struct request *req)
> struct nvme_loop_iod *iod = blk_mq_rq_to_pdu(req);
>
> sg_free_table_chained(&iod->sg_table, NVME_INLINE_SG_CNT);
> - nvme_complete_rq(req);
> +
> + if (req->mq_hctx->type != HCTX_TYPE_POLL || !in_interrupt())
> + nvme_complete_rq(req);
> + else
> + queue_work(nvmet_wq, &iod->poll);
> }
>
> static struct blk_mq_tags *nvme_loop_tagset(struct nvme_loop_queue *queue)
> @@ -120,6 +126,15 @@ static void nvme_loop_queue_response(struct nvmet_req *req)
> }
> }
>
> +static void nvme_loop_poll_work(struct work_struct *work)
> +{
> + struct nvme_loop_iod *iod =
> + container_of(work, struct nvme_loop_iod, poll);
> + struct request *req = blk_mq_rq_from_pdu(iod);
> +
> + nvme_complete_rq(req);
> +}
> +
> static void nvme_loop_execute_work(struct work_struct *work)
> {
> struct nvme_loop_iod *iod =
> @@ -170,6 +185,30 @@ static blk_status_t nvme_loop_queue_rq(struct blk_mq_hw_ctx *hctx,
> return BLK_STS_OK;
> }
>
> +static bool nvme_loop_poll_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)
> +{
> + struct blk_mq_hw_ctx *hctx = data;
> + struct nvme_loop_iod *iod;
> + struct request *rq;
> +
> + rq = blk_mq_tag_to_rq(hctx->tags, bitnr);
> + if (!rq)
> + return true;
> +
> + iod = blk_mq_rq_to_pdu(rq);
> + flush_work(&iod->poll);
If we want to go down this route, I would think that maybe
it'd be better to add .poll to nvmet_req like .execute, that can
actually be wired to bio_poll ? for file it can be wired to fop.iopoll
next prev parent reply other threads:[~2023-03-22 7:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 0:23 [PATCH 0/3] nvme fabrics polling fixes Keith Busch
2023-03-22 0:23 ` [PATCH 1/3] nvme-fabrics: add queue setup helpers Keith Busch
2023-03-22 1:46 ` Chaitanya Kulkarni
2023-03-22 4:38 ` kernel test robot
2023-03-22 5:21 ` Chaitanya Kulkarni
2023-03-22 7:35 ` Sagi Grimberg
2023-03-22 8:27 ` Christoph Hellwig
2023-03-22 9:07 ` Sagi Grimberg
2023-03-22 9:25 ` kernel test robot
2023-03-22 0:23 ` [PATCH 2/3] nvme: add polling options for loop target Keith Busch
2023-03-22 1:47 ` Chaitanya Kulkarni
2023-03-22 7:44 ` Sagi Grimberg [this message]
2023-03-22 8:23 ` Christoph Hellwig
2023-03-22 8:46 ` Daniel Wagner
2023-03-22 13:52 ` Christoph Hellwig
2023-03-22 14:06 ` Daniel Wagner
2023-03-22 14:20 ` Christoph Hellwig
2023-03-22 14:30 ` Keith Busch
2023-03-22 0:23 ` [PATCH 3/3] blk-mq: directly poll requests Keith Busch
2023-03-22 7:36 ` Sagi Grimberg
2023-03-22 8:23 ` Christoph Hellwig
2023-03-22 9:08 ` Sagi Grimberg
2023-03-22 8:37 ` Daniel Wagner
2023-03-22 18:16 ` Chaitanya Kulkarni
2023-03-31 7:57 ` Shinichiro Kawasaki
2023-03-22 7:31 ` [PATCH 0/3] nvme fabrics polling fixes Sagi Grimberg
2023-03-22 8:48 ` Daniel Wagner
2023-03-22 13:24 ` 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=6c5bddde-7a9e-c7be-4302-ce0334708914@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@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