From: Keith Busch <kbusch@kernel.org>
To: Po-Wen Kao <powen.kao@mediatek.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
wsd_upstream@mediatek.com, peter.wang@mediatek.com,
stanley.chu@mediatek.com, alice.chao@mediatek.com,
naomi.chu@mediatek.com, chun-hung.wu@mediatek.com,
cc.chou@mediatek.com, eddie.huang@mediatek.com,
Ed Tsai <ed.tsai@mediatek.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v1 1/1] nvme: complete directly for hctx with only one ctx mapping
Date: Tue, 30 May 2023 11:45:49 -0600 [thread overview]
Message-ID: <ZHY2TUrKVBj2xGE2@kbusch-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20230530024120.17196-1-powen.kao@mediatek.com>
On Tue, May 30, 2023 at 10:41:19AM +0800, Po-Wen Kao wrote:
> ---
> block/blk-mq.c | 8 +++-----
> drivers/nvme/host/nvme.h | 4 ++++
> 2 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 1749f5890606..b60c78f5ad46 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -1181,12 +1181,10 @@ bool blk_mq_complete_request_remote(struct request *rq)
> WRITE_ONCE(rq->state, MQ_RQ_COMPLETE);
>
> /*
> - * For request which hctx has only one ctx mapping,
> - * or a polled request, always complete locally,
> - * it's pointless to redirect the completion.
> + * For a polled request, always complete locally, it's pointless
> + * to redirect the completion.
> */
> - if (rq->mq_hctx->nr_ctx == 1 ||
> - rq->cmd_flags & REQ_POLLED)
> + if (rq->cmd_flags & REQ_POLLED)
> return false;
>
> if (blk_mq_complete_need_ipi(rq)) {
> diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
> index 7cf8e44d135e..acc9b1ce071d 100644
> --- a/drivers/nvme/host/nvme.h
> +++ b/drivers/nvme/host/nvme.h
> @@ -702,6 +702,10 @@ static inline bool nvme_try_complete_req(struct request *req, __le16 status,
> nvme_should_fail(req);
> if (unlikely(blk_should_fake_timeout(req->q)))
> return true;
> + if (likely(req->mq_hctx->nr_ctx == 1)) {
> + WRITE_ONCE(req->state, MQ_RQ_COMPLETE);
> + return false;
> + }
I don't think we want low level drivers directly messing with blk-mq
request state.
Is the early nr_ctx check optimisation really worth it? Would the
following work for your use case?
---
diff --git a/block/blk-mq.c b/block/blk-mq.c
index f6dad0886a2fa..a2d65bb127e29 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -1176,7 +1176,8 @@ bool blk_mq_complete_request_remote(struct request *rq)
* or a polled request, always complete locally,
* it's pointless to redirect the completion.
*/
- if (rq->mq_hctx->nr_ctx == 1 ||
+ if ((rq->mq_hctx->nr_ctx == 1 &&
+ rq->mq_ctx->cpu == raw_smp_processor_id()) ||
rq->cmd_flags & REQ_POLLED)
return false;
--
next prev parent reply other threads:[~2023-05-30 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 2:41 Po-Wen Kao
2023-05-30 2:49 ` Stanley Chu
2023-05-30 17:45 ` Keith Busch [this message]
2023-05-31 1:14 ` Ed Tsai (蔡宗軒)
2023-05-31 1:32 ` Ed Tsai (蔡宗軒)
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=ZHY2TUrKVBj2xGE2@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=alice.chao@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=axboe@kernel.dk \
--cc=cc.chou@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=ed.tsai@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=naomi.chu@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=powen.kao@mediatek.com \
--cc=sagi@grimberg.me \
--cc=stanley.chu@mediatek.com \
--cc=wsd_upstream@mediatek.com \
/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
all inboxes | Powered by JetHome®