From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 0/3] update request retries (loop, rdma, fc)
Date: Wed, 29 Mar 2017 21:00:24 +0300 [thread overview]
Message-ID: <1490810427-27776-1-git-send-email-sagi@grimberg.me> (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
next reply other threads:[~2017-03-29 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 18:00 Sagi Grimberg [this message]
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
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=1490810427-27776-1-git-send-email-sagi@grimberg.me \
--to=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;
as well as URLs for NNTP newsgroup(s).