From: Jens Axboe <axboe@kernel.dk>
To: "Keith Busch" <keith.busch@intel.com>, "Matias Bjørling" <m@bjorling.me>
Cc: willy@linux.intel.com, sbradshaw@micron.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] NVMe: basic conversion to blk-mq
Date: Thu, 29 May 2014 13:33:58 -0600 [thread overview]
Message-ID: <53878BA6.7050907@kernel.dk> (raw)
In-Reply-To: <53878B5D.8040508@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
On 05/29/2014 01:32 PM, Jens Axboe wrote:
> On 05/29/2014 08:25 AM, Jens Axboe wrote:
>>>> +static int nvme_submit_flush_sync(struct nvme_queue *nvmeq, struct
>>>> nvme_ns *ns)
>>>> +{
>>>> + struct request *req;
>>>> + struct nvme_command cmnd;
>>>> +
>>>> + req = blk_mq_alloc_request(ns->queue, WRITE, GFP_KERNEL, false);
>>>> + if (!req)
>>>> + return -ENOMEM;
>>>> +
>>>> + nvme_setup_flush(&cmnd, ns, req->tag);
>>>> + nvme_submit_sync_cmd(req, &cmnd, NULL, NVME_IO_TIMEOUT);
>>>>
>>>> return 0;
>>>> }
>>>
>>> It looks like this function above is being called from an interrupt
>>> context where we are already holding a spinlock. The sync command will
>>> try to take that same lock.
>>
>> Yes, that code still looks very buggy. The initial alloc for
>> flush_cmd_info should also retry, not fail hard, if that alloc fails.
>> For the reinsert part, Matias, you want to look at the flush code in
>> blk-mq and how that handles it.
>
> There's an easy fix for this. Once it's managed by blk-mq, blk-mq will
> decompose requests for you. This means a flush with data will be turned
> into two commands for you, so we can kill this code attempting to handle
> flush request with data.
>
> Patch attached. Depending on how the series needs to look, the prep
> patch of support bio flush with data should just be dropped however. No
> point in adding that, and the removing it again.
Updated, we can kill the flush_cmd_info struct as well.
--
Jens Axboe
[-- Attachment #2: nvme-flush-v2.patch --]
[-- Type: text/x-patch, Size: 2177 bytes --]
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index ac695b336a98..4cd525ee5f4a 100644
--- a/drivers/block/nvme-core.c
+++ b/drivers/block/nvme-core.c
@@ -513,35 +513,6 @@ static void nvme_submit_flush(struct nvme_queue *nvmeq, struct nvme_ns *ns,
writel(nvmeq->sq_tail, nvmeq->q_db);
}
-static int nvme_submit_flush_sync(struct nvme_queue *nvmeq, struct nvme_ns *ns)
-{
- struct request *req;
- struct nvme_command cmnd;
-
- req = blk_mq_alloc_request(ns->queue, WRITE, GFP_KERNEL, false);
- if (!req)
- return -ENOMEM;
-
- nvme_setup_flush(&cmnd, ns, req->tag);
- nvme_submit_sync_cmd(req, &cmnd, NULL, NVME_IO_TIMEOUT);
-
- return 0;
-}
-
-struct flush_cmd_info {
- struct nvme_ns *ns;
- struct nvme_iod *iod;
-};
-
-static void req_flush_completion(struct nvme_queue *nvmeq, void *ctx,
- struct nvme_completion *cqe)
-{
- struct flush_cmd_info *flush_cmd = ctx;
- nvme_submit_flush_sync(nvmeq, flush_cmd->ns);
- req_completion(nvmeq, flush_cmd->iod, cqe);
- kfree(flush_cmd);
-}
-
static int nvme_submit_iod(struct nvme_queue *nvmeq, struct nvme_iod *iod,
struct nvme_ns *ns)
{
@@ -560,7 +531,7 @@ static int nvme_submit_iod(struct nvme_queue *nvmeq, struct nvme_iod *iod,
nvme_submit_discard(nvmeq, ns, req, iod);
goto end_submit;
}
- if (req->cmd_flags & REQ_FLUSH && !iod->nents) {
+ if (req->cmd_flags & REQ_FLUSH) {
nvme_submit_flush(nvmeq, ns, req->tag);
goto end_submit;
}
@@ -615,16 +586,6 @@ static int nvme_submit_req_queue(struct nvme_queue *nvmeq, struct nvme_ns *ns,
nvme_set_info(cmd, iod, req_completion);
- if ((req->cmd_flags & REQ_FLUSH) && psegs) {
- struct flush_cmd_info *flush_cmd = kmalloc(
- sizeof(struct flush_cmd_info), GFP_KERNEL);
- if (!flush_cmd)
- goto free_iod;
- flush_cmd->ns = ns;
- flush_cmd->iod = iod;
- nvme_set_info(cmd, flush_cmd, req_flush_completion);
- }
-
if (req->cmd_flags & REQ_DISCARD) {
void *range;
/*
@@ -655,7 +616,6 @@ static int nvme_submit_req_queue(struct nvme_queue *nvmeq, struct nvme_ns *ns,
finish_cmd:
nvme_finish_cmd(nvmeq, req->tag, NULL);
- free_iod:
nvme_free_iod(nvmeq->dev, iod);
return BLK_MQ_RQ_QUEUE_ERROR;
}
next prev parent reply other threads:[~2014-05-29 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 22:59 [PATCH V3] basic conversion to blk-mq Matias Bjørling
2014-05-28 22:59 ` [PATCH V3] NVMe: " Matias Bjørling
2014-05-29 3:07 ` Keith Busch
2014-05-29 14:25 ` Jens Axboe
2014-05-29 19:32 ` Jens Axboe
2014-05-29 19:33 ` Jens Axboe [this message]
2014-05-29 22:34 ` Keith Busch
2014-05-29 23:06 ` Jens Axboe
2014-05-29 23:12 ` Jens Axboe
2014-05-30 17:20 ` Matias Bjorling
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=53878BA6.7050907@kernel.dk \
--to=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bjorling.me \
--cc=sbradshaw@micron.com \
--cc=willy@linux.intel.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