* [PATCH 0/3] update request retries (loop, rdma, fc)
@ 2017-03-29 18:00 Sagi Grimberg
2017-03-29 18:00 ` [PATCH 1/3] nvme-rdma: increment request retries counter before requeuing Sagi Grimberg
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Sagi Grimberg @ 2017-03-29 18:00 UTC (permalink / raw)
Keep a consistent behavior with what's checked in the core which
does not requeue if we exhausted nvme_max_retries.
Sagi Grimberg (3):
nvme-rdma: increment request retries counter before requeuing
nvme-loop: increment request retries counter before requeuing
nvme-fc: increment request retries counter before requeuing
drivers/nvme/host/fc.c | 1 +
drivers/nvme/host/rdma.c | 1 +
drivers/nvme/target/loop.c | 1 +
3 files changed, 3 insertions(+)
--
2.7.4
^ permalink raw reply [flat|nested] 8+ messages in thread* [PATCH 1/3] nvme-rdma: increment request retries counter before requeuing
2017-03-29 18:00 [PATCH 0/3] update request retries (loop, rdma, fc) Sagi Grimberg
@ 2017-03-29 18:00 ` Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-29 18:00 ` [PATCH 2/3] nvme-loop: " Sagi Grimberg
` (2 subsequent siblings)
3 siblings, 1 reply; 8+ messages in thread
From: Sagi Grimberg @ 2017-03-29 18:00 UTC (permalink / raw)
This way our max retry limit holds as well.
Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
---
drivers/nvme/host/rdma.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
index a92791c485d1..c8f703e68d73 100644
--- a/drivers/nvme/host/rdma.c
+++ b/drivers/nvme/host/rdma.c
@@ -1526,6 +1526,7 @@ static void nvme_rdma_complete_rq(struct request *rq)
if (unlikely(rq->errors)) {
if (nvme_req_needs_retry(rq, rq->errors)) {
+ rq->retries++;
nvme_requeue_req(rq);
return;
}
--
2.7.4
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH 2/3] nvme-loop: increment request retries counter before requeuing
2017-03-29 18:00 [PATCH 0/3] update request retries (loop, rdma, fc) Sagi Grimberg
2017-03-29 18:00 ` [PATCH 1/3] nvme-rdma: increment request retries counter before requeuing Sagi Grimberg
@ 2017-03-29 18:00 ` Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-29 18:00 ` [PATCH 3/3] nvme-fc: " Sagi Grimberg
2017-03-30 11:23 ` [PATCH 0/3] update request retries (loop, rdma, fc) Christoph Hellwig
3 siblings, 1 reply; 8+ messages in thread
From: Sagi Grimberg @ 2017-03-29 18:00 UTC (permalink / raw)
This way our max retry limit holds as well.
Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
---
drivers/nvme/target/loop.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/nvme/target/loop.c b/drivers/nvme/target/loop.c
index 227a5320879e..6a54e387379e 100644
--- a/drivers/nvme/target/loop.c
+++ b/drivers/nvme/target/loop.c
@@ -98,6 +98,7 @@ static void nvme_loop_complete_rq(struct request *req)
if (unlikely(req->errors)) {
if (nvme_req_needs_retry(req, req->errors)) {
+ req->retries++;
nvme_requeue_req(req);
return;
}
--
2.7.4
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH 3/3] nvme-fc: increment request retries counter before requeuing
2017-03-29 18:00 [PATCH 0/3] update request retries (loop, rdma, fc) Sagi Grimberg
2017-03-29 18:00 ` [PATCH 1/3] nvme-rdma: increment request retries counter before requeuing Sagi Grimberg
2017-03-29 18:00 ` [PATCH 2/3] nvme-loop: " Sagi Grimberg
@ 2017-03-29 18:00 ` Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-30 11:23 ` [PATCH 0/3] update request retries (loop, rdma, fc) Christoph Hellwig
3 siblings, 1 reply; 8+ messages in thread
From: Sagi Grimberg @ 2017-03-29 18:00 UTC (permalink / raw)
This way our max retry limit holds as well.
Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
---
drivers/nvme/host/fc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c
index 331ae9f8924d..2987f5ecd496 100644
--- a/drivers/nvme/host/fc.c
+++ b/drivers/nvme/host/fc.c
@@ -1935,6 +1935,7 @@ nvme_fc_complete_rq(struct request *rq)
if (unlikely(rq->errors)) {
if (nvme_req_needs_retry(rq, rq->errors)) {
+ rq->retries++;
nvme_requeue_req(rq);
return;
}
--
2.7.4
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH 0/3] update request retries (loop, rdma, fc)
2017-03-29 18:00 [PATCH 0/3] update request retries (loop, rdma, fc) Sagi Grimberg
` (2 preceding siblings ...)
2017-03-29 18:00 ` [PATCH 3/3] nvme-fc: " Sagi Grimberg
@ 2017-03-30 11:23 ` Christoph Hellwig
3 siblings, 0 replies; 8+ messages in thread
From: Christoph Hellwig @ 2017-03-30 11:23 UTC (permalink / raw)
On Wed, Mar 29, 2017@09:00:24PM +0300, Sagi Grimberg wrote:
> Keep a consistent behavior with what's checked in the core which
> does not requeue if we exhausted nvme_max_retries.
Looks fine:
Reviewed-by: Christoph Hellwig <hch at lst.de>
But we really need to move this to common code. I'll send a series
to do that, but it will be on top of your series.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-03-30 11:23 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-29 18:00 [PATCH 0/3] update request retries (loop, rdma, fc) Sagi Grimberg
2017-03-29 18:00 ` [PATCH 1/3] nvme-rdma: increment request retries counter before requeuing Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-29 18:00 ` [PATCH 2/3] nvme-loop: " Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-29 18:00 ` [PATCH 3/3] nvme-fc: " Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-30 11:23 ` [PATCH 0/3] update request retries (loop, rdma, fc) Christoph Hellwig
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).