From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH v4 1/4] nvmet-rdma: +1 to *queue_size from hsqsize/hrqsize
Date: Thu, 18 Aug 2016 08:56:50 -0700 [thread overview]
Message-ID: <1471535810.31578.8.camel@linux.intel.com> (raw)
In-Reply-To: <7b7f2836-ad77-b508-ad53-2f49aec03612@grimberg.me>
On Thu, 2016-08-18@10:00 +0300, Sagi Grimberg wrote:
>
> On 18/08/16 01:00, Jay Freyensee wrote:
> >
> > The host will be sending sqsize 0-based values,
> > the target need to be adjusted as well.
> >
> > Signed-off-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
> > Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
> > ---
> > ?drivers/nvme/target/rdma.c | 8 ++++----
> > ?1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/nvme/target/rdma.c
> > b/drivers/nvme/target/rdma.c
> > index e06d504..68b7b04 100644
> > --- a/drivers/nvme/target/rdma.c
> > +++ b/drivers/nvme/target/rdma.c
> > @@ -1004,11 +1004,11 @@ nvmet_rdma_parse_cm_connect_req(struct
> > rdma_conn_param *conn,
> > ? queue->host_qid = le16_to_cpu(req->qid);
> >
> > ? /*
> > - ?* req->hsqsize corresponds to our recv queue size
> > - ?* req->hrqsize corresponds to our send queue size
> > + ?* req->hsqsize corresponds to our recv queue size plus 1
> > + ?* req->hrqsize corresponds to our send queue size plus 1
> > ? ?*/
> > - queue->recv_queue_size = le16_to_cpu(req->hsqsize);
> > - queue->send_queue_size = le16_to_cpu(req->hrqsize);
> > + queue->recv_queue_size = le16_to_cpu(req->hsqsize) + 1;
> > + queue->send_queue_size = le16_to_cpu(req->hrqsize) + 1;
>
> hrqsize is sent as is (1's based) so no need to increment.
> I'll fix it...
The target's send and receive queue size will be still the same length
and I thought we wanted to make the queue associated with hrqsize 1
entry larger more than the queue associated with hsqsize.
Either case, I'm fine with the solution, when the specification
actually explains how to use this better, we can re-visit.
next prev parent reply other threads:[~2016-08-18 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 22:00 [PATCH v4 0/4] sqsize fixes Jay Freyensee
2016-08-17 22:00 ` [PATCH v4 1/4] nvmet-rdma: +1 to *queue_size from hsqsize/hrqsize Jay Freyensee
2016-08-18 7:00 ` Sagi Grimberg
2016-08-18 15:56 ` J Freyensee [this message]
2016-08-17 22:00 ` [PATCH v4 2/4] fabrics: define admin sqsize min default, per spec Jay Freyensee
2016-08-17 22:00 ` [PATCH v4 3/4] nvme-rdma: fix sqsize/hsqsize " Jay Freyensee
2016-08-17 22:00 ` [PATCH v4 4/4] nvme-loop: set sqsize to 0-based value, " 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=1471535810.31578.8.camel@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).