From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH v2 1/5] fabrics: define admin sqsize min default, per spec
Date: Tue, 16 Aug 2016 11:59:10 +0300 [thread overview]
Message-ID: <b355143d-a431-d4a4-ca55-a896f5d57956@grimberg.me> (raw)
In-Reply-To: <1471279659-25951-2-git-send-email-james_p_freyensee@linux.intel.com>
On 15/08/16 19:47, Jay Freyensee wrote:
> Upon admin queue connect(), the rdma qp was being
> set based on NVMF_AQ_DEPTH. However, the fabrics layer was
> using the sqsize field value set for I/O queues for the admin
> queue, which threw the nvme layer and rdma layer off-whack:
>
> root at fedora23-fabrics-host1 nvmf]# dmesg
> [ 3507.798642] nvme_fabrics: nvmf_connect_admin_queue():admin sqsize
> being sent is: 128
> [ 3507.798858] nvme nvme0: creating 16 I/O queues.
> [ 3507.896407] nvme nvme0: new ctrl: NQN "nullside-nqn", addr
> 192.168.1.3:4420
>
> Thus, to have a different admin queue value, we use
> NVMF_AQ_DEPTH for connect() and RDMA private data
> as the minimum depth specified in the NVMe-over-Fabrics 1.0 spec.
>
> Reported-by: Daniel Verkamp <daniel.verkamp at intel.com>
> Signed-off-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
> Reviewed-by: Daniel Verkamp <daniel.verkamp at intel.com>
> ---
> drivers/nvme/host/fabrics.c | 9 ++++++++-
> drivers/nvme/host/rdma.c | 13 +++++++++++--
> 2 files changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
> index dc99676..020302c 100644
> --- a/drivers/nvme/host/fabrics.c
> +++ b/drivers/nvme/host/fabrics.c
> @@ -363,7 +363,14 @@ int nvmf_connect_admin_queue(struct nvme_ctrl *ctrl)
> cmd.connect.opcode = nvme_fabrics_command;
> cmd.connect.fctype = nvme_fabrics_type_connect;
> cmd.connect.qid = 0;
> - cmd.connect.sqsize = cpu_to_le16(ctrl->sqsize);
> +
> + /*
> + * fabrics spec sets a minimum of depth 32 for admin queue,
> + * so set the queue with this depth always until
> + * justification otherwise.
> + */
> + cmd.connect.sqsize = cpu_to_le16(NVMF_AQ_DEPTH - 1);
> +
Better to keep this part as a stand-alone patch for fabrics.
> /*
> * Set keep-alive timeout in seconds granularity (ms * 1000)
> * and add a grace period for controller kato enforcement
> diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
> index 3e3ce2b..168cd23 100644
> --- a/drivers/nvme/host/rdma.c
> +++ b/drivers/nvme/host/rdma.c
> @@ -1284,8 +1284,17 @@ 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);
> + /*
> + * set the admin queue depth to the minimum size
> + * specified by the Fabrics standard.
> + */
> + if (priv.qid == 0) {
> + priv.hrqsize = cpu_to_le16(NVMF_AQ_DEPTH - 1);
> + priv.hsqsize = cpu_to_le16(NVMF_AQ_DEPTH - 1);
> + } else {
> + priv.hrqsize = cpu_to_le16(queue->queue_size);
> + priv.hsqsize = cpu_to_le16(queue->queue_size);
> + }
This should be squashed with the next patch.
next prev parent reply other threads:[~2016-08-16 8:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 16:47 [PATCH v2 0/5] sqsize fixes Jay Freyensee
2016-08-15 16:47 ` [PATCH v2 1/5] fabrics: define admin sqsize min default, per spec Jay Freyensee
2016-08-16 8:59 ` Sagi Grimberg [this message]
2016-08-16 16:19 ` J Freyensee
2016-08-15 16:47 ` [PATCH v2 2/5] nvme-rdma: fix sqsize/hsqsize " Jay Freyensee
2016-08-16 8:57 ` Sagi Grimberg
2016-08-16 16:20 ` J Freyensee
2016-08-15 16:47 ` [PATCH v2 3/5] nvmet-rdma: +1 to *queue_size from hsqsize/hrqsize Jay Freyensee
2016-08-16 8:56 ` Sagi Grimberg
2016-08-16 16:22 ` J Freyensee
2016-08-15 16:47 ` [PATCH v2 4/5] nvme-loop: set sqsize to 0-based value, per spec Jay Freyensee
2016-08-16 8:59 ` Sagi Grimberg
2016-08-16 16:22 ` J Freyensee
2016-08-15 16:47 ` [PATCH v2 5/5] nvme-rdma: adjust hrqsize to plus 1 Jay Freyensee
2016-08-16 9:05 ` Sagi Grimberg
2016-08-16 16:34 ` J 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=b355143d-a431-d4a4-ca55-a896f5d57956@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).