From: james_p_freyensee@linux.intel.com (Jay Freyensee)
Subject: [PATCH RFC 2/4] nvme-rdma: fix sqsize/hsqsize/hrqsize per spec
Date: Wed, 10 Aug 2016 21:07:16 -0700 [thread overview]
Message-ID: <1470888438-823-3-git-send-email-james_p_freyensee@linux.intel.com> (raw)
In-Reply-To: <1470888438-823-1-git-send-email-james_p_freyensee@linux.intel.com>
Per NVMe-over-Fabrics 1.0 spec, sqsize is represented as
a 0-based value.
Also per spec, the RDMA binding values shall be set
to sqsize, which makes hsqsize 0-based values.
Also per spec, but not very clear, is hrqsize is +1
of hsqsize.
Thus, the sqsize during NVMf connect() is now:
[root at fedora23-fabrics-host1 for-48]# dmesg
[ 318.720645] nvme_fabrics: nvmf_connect_admin_queue(): sqsize for
admin queue: 31
[ 318.720884] nvme nvme0: creating 16 I/O queues.
[ 318.810114] nvme_fabrics: nvmf_connect_io_queue(): sqsize for i/o
queue: 127
Reported-by: Daniel Verkamp <daniel.verkamp at intel.com>
Signed-off-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
---
drivers/nvme/host/rdma.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
index 3e3ce2b..8be64f1 100644
--- a/drivers/nvme/host/rdma.c
+++ b/drivers/nvme/host/rdma.c
@@ -1284,8 +1284,21 @@ static int nvme_rdma_route_resolved(struct nvme_rdma_queue *queue)
priv.recfmt = cpu_to_le16(NVME_RDMA_CM_FMT_1_0);
priv.qid = cpu_to_le16(nvme_rdma_queue_idx(queue));
- priv.hrqsize = cpu_to_le16(queue->queue_size);
- priv.hsqsize = cpu_to_le16(queue->queue_size);
+
+ /*
+ * On one end, the fabrics spec is pretty clear that
+ * hsqsize variables shall be set to the value of sqsize,
+ * which is a 0-based number. What is confusing is the value for
+ * hrqsize. After clarification from NVMe spec committee member,
+ * the minimum value of hrqsize is hsqsize+1.
+ */
+ if (priv.qid == 0) {
+ priv.hsqsize = cpu_to_le16(queue->ctrl->ctrl.admin_sqsize);
+ priv.hrqsize = cpu_to_le16(queue->ctrl->ctrl.admin_sqsize+1);
+ } else {
+ priv.hsqsize = cpu_to_le16(queue->ctrl->ctrl.sqsize);
+ priv.hrqsize = cpu_to_le16(queue->ctrl->ctrl.sqsize+1);
+ }
ret = rdma_connect(queue->cm_id, ¶m);
if (ret) {
@@ -1907,7 +1920,7 @@ static struct nvme_ctrl *nvme_rdma_create_ctrl(struct device *dev,
spin_lock_init(&ctrl->lock);
ctrl->queue_count = opts->nr_io_queues + 1; /* +1 for admin queue */
- ctrl->ctrl.sqsize = opts->queue_size;
+ ctrl->ctrl.sqsize = opts->queue_size-1;
ctrl->ctrl.kato = opts->kato;
ret = -ENOMEM;
--
2.7.4
next prev parent reply other threads:[~2016-08-11 4:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 4:07 [PATCH RFC 0/4] sqsize zero-based fixes Jay Freyensee
2016-08-11 4:07 ` [PATCH RFC 1/4] fabrics: define admin sqsize min default, per spec Jay Freyensee
2016-08-11 9:01 ` Sagi Grimberg
2016-08-11 15:08 ` Christoph Hellwig
2016-08-11 16:33 ` J Freyensee
2016-08-11 4:07 ` Jay Freyensee [this message]
2016-08-11 7:03 ` [PATCH RFC 2/4] nvme-rdma: fix sqsize/hsqsize/hrqsize " Sagi Grimberg
2016-08-11 16:35 ` J Freyensee
2016-08-11 15:21 ` Christoph Hellwig
2016-08-11 16:40 ` J Freyensee
2016-08-11 23:24 ` J Freyensee
2016-08-11 4:07 ` [PATCH RFC 3/4] nvmet-rdma: +1 to *queue_size from hsqsize/hrqsize Jay Freyensee
2016-08-11 4:07 ` [PATCH RFC 4/4] nvme-loop: set sqsize to 0-based value, per spec Jay Freyensee
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=1470888438-823-3-git-send-email-james_p_freyensee@linux.intel.com \
--to=james_p_freyensee@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;
as well as URLs for NNTP newsgroup(s).