From: Minwoo Im <minwoo.im.dev@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Minwoo Im <minwoo.im.dev@gmail.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: [PATCH 3/3] nvme: add parameter command_retry to enable retry
Date: Fri, 8 Jan 2021 23:46:59 +0900 [thread overview]
Message-ID: <20210108144659.7126-4-minwoo.im.dev@gmail.com> (raw)
In-Reply-To: <20210108144659.7126-1-minwoo.im.dev@gmail.com>
nvme_init_request() has set REQ_FAILFAST_DRIVER to make requests
non-retryable. This command flag value is checked in
nvme_decide_disposition() to decide whether to RETRY or other
operations. In that point, blk_noretry_request() macro will be used to
check if command flags have one of REQ_FAILFAST_*. If so, it just
decides to complete the request without retrying.
This patch added a module parameter named command_retry to turn on the
command retry feature in this driver. If turning it on,
REQ3_FAILFAST_DRIVER will not be set to requests so that retry can be
reached out to nvme_retry_req() based on the module parameter.
Signed-off-by: Minwoo Im <minwoo.im.dev@gmail.com>
---
drivers/nvme/host/core.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 6e428fdc25a8..e1836ca9956f 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -44,6 +44,10 @@ static unsigned char shutdown_timeout = 5;
module_param(shutdown_timeout, byte, 0644);
MODULE_PARM_DESC(shutdown_timeout, "timeout in seconds for controller shutdown");
+static bool command_retry;
+module_param(command_retry, bool, 0644);
+MODULE_PARM_DESC(command_retry, "retry commands up to nvme_max_retries");
+
static u8 nvme_max_retries = 5;
module_param_named(max_retries, nvme_max_retries, byte, 0644);
MODULE_PARM_DESC(max_retries, "max number of retries a command may have");
@@ -560,7 +564,8 @@ static inline void nvme_init_request(struct request *req,
else /* no queuedata implies admin queue */
req->timeout = NVME_ADMIN_TIMEOUT;
- req->cmd_flags |= REQ_FAILFAST_DRIVER;
+ if (!command_retry)
+ req->cmd_flags |= REQ_FAILFAST_DRIVER;
nvme_clear_nvme_request(req);
nvme_req(req)->cmd = cmd;
}
--
2.17.1
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-08 14:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 14:46 [PATCH 0/3] nvme: fixes for command retry Minwoo Im
2021-01-08 14:46 ` [PATCH 1/3] nvme: support command retry delay for admin command Minwoo Im
2021-01-09 20:34 ` Chaitanya Kulkarni
2021-01-10 1:33 ` Minwoo Im
2021-01-12 8:06 ` Christoph Hellwig
2021-01-12 8:06 ` Christoph Hellwig
2021-01-12 8:47 ` Minwoo Im
2021-01-14 7:22 ` Christoph Hellwig
2021-01-15 18:40 ` Minwoo Im
2021-01-08 14:46 ` [PATCH 2/3] nvme: check all retry delay times in Identify Controller Minwoo Im
2021-01-12 8:08 ` Christoph Hellwig
2021-01-12 8:40 ` Minwoo Im
2021-01-08 14:46 ` Minwoo Im [this message]
2021-01-11 3:47 ` [PATCH 3/3] nvme: add parameter command_retry to enable retry Chao Leng
2021-01-11 12:27 ` Minwoo Im
2021-01-12 9:34 ` Chao Leng
2021-01-12 11:28 ` Minwoo Im
2021-01-12 8:09 ` Christoph Hellwig
2021-01-12 8:44 ` Minwoo Im
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=20210108144659.7126-4-minwoo.im.dev@gmail.com \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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