From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v2] nvmet: protect sqhd update by a lock
Date: Mon, 16 Oct 2017 08:18:20 -0700 [thread overview]
Message-ID: <20171016151820.14766-1-jsmart2021@gmail.com> (raw)
In testing target io in read write mix, we did indeed get into cases
where sqhd didn't update properly and slowly missed enough updates to
shutdown the queue.
Protect the read/modify/set update of sqhd under a lock for coherency.
Signed-off-by: James Smart <james.smart at broadcom.com>
---
v2: move locks so around update and assignment
drivers/nvme/target/core.c | 5 +++++
drivers/nvme/target/nvmet.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
index cfc35cbb6fe2..28300e9bbef1 100644
--- a/drivers/nvme/target/core.c
+++ b/drivers/nvme/target/core.c
@@ -387,12 +387,16 @@ struct nvmet_ns *nvmet_ns_alloc(struct nvmet_subsys *subsys, u32 nsid)
static void __nvmet_req_complete(struct nvmet_req *req, u16 status)
{
+ unsigned long flags;
+
if (status)
nvmet_set_status(req, status);
+ spin_lock_irqsave(&req->sq->sqhd_lock, flags);
if (req->sq->size)
req->sq->sqhd = (req->sq->sqhd + 1) % req->sq->size;
req->rsp->sq_head = cpu_to_le16(req->sq->sqhd);
+ spin_unlock_irqrestore(&req->sq->sqhd_lock, flags);
req->rsp->sq_id = cpu_to_le16(req->sq->qid);
req->rsp->command_id = req->cmd->common.command_id;
@@ -425,6 +429,7 @@ void nvmet_sq_setup(struct nvmet_ctrl *ctrl, struct nvmet_sq *sq,
sq->size = size;
ctrl->sqs[qid] = sq;
+ spin_lock_init(&sq->sqhd_lock);
}
static void nvmet_confirm_sq(struct percpu_ref *ref)
diff --git a/drivers/nvme/target/nvmet.h b/drivers/nvme/target/nvmet.h
index ed38b44a7007..bdb904bdf676 100644
--- a/drivers/nvme/target/nvmet.h
+++ b/drivers/nvme/target/nvmet.h
@@ -77,6 +77,7 @@ struct nvmet_sq {
u16 sqhd;
struct completion free_done;
struct completion confirm_done;
+ spinlock_t sqhd_lock;
};
/**
--
2.13.1
next reply other threads:[~2017-10-16 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 15:18 James Smart [this message]
2017-10-16 15:31 ` [PATCH v2] nvmet: protect sqhd update by a lock Johannes Thumshirn
2017-10-17 6:43 ` Christoph Hellwig
2017-10-17 14:19 ` James Smart
2017-10-18 7:23 ` Christoph Hellwig
2017-10-18 16:45 ` James Smart
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=20171016151820.14766-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.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;
as well as URLs for NNTP newsgroup(s).