From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvmet: implement valid sqhd values in completions
Date: Thu, 14 Sep 2017 10:01:39 -0700 [thread overview]
Message-ID: <20170914170139.GA25583@infradead.org> (raw)
In-Reply-To: <20170907201836.25067-1-jsmart2021@gmail.com>
On Thu, Sep 07, 2017@01:18:36PM -0700, James Smart wrote:
> To support sqhd, for initiators that are following the spec and
> paying attention to sqhd vs their sqtail values:
> - add sqhd to struct nvmet_sq
> - initialize sqhd to 0 in nvmet_sq_setup
> - rather than propagate the 0's-based qsize value from the connect message
> which requires a +1 in every sqhd update, and as nothing else references
> it, convert to 1's-based value in nvmt_sq/cq_setup() calls.
> - validate connect message sqsize being non-zero per spec.
> - updated assign sqhd for every completion that goes back.
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
> ---
> drivers/nvme/target/core.c | 9 +++++----
> drivers/nvme/target/fabrics-cmd.c | 9 +++++++--
> drivers/nvme/target/nvmet.h | 1 +
> 3 files changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
> index 7c23eaf8e563..434394ead4a2 100644
> --- a/drivers/nvme/target/core.c
> +++ b/drivers/nvme/target/core.c
> @@ -390,8 +390,8 @@ static void __nvmet_req_complete(struct nvmet_req *req, u16 status)
> if (status)
> nvmet_set_status(req, status);
>
> - /* XXX: need to fill in something useful for sq_head */
> - req->rsp->sq_head = 0;
> + req->sq->sqhd = (req->sq->sqhd + 1) % req->sq->size;
> + req->rsp->sq_head = req->sq->sqhd;
This is missing an endianes conversion:
drivers/nvme/target/core.c:394:27: warning: incorrect type in assignment (different base types)
drivers/nvme/target/core.c:394:27: expected restricted __le16 [usertype] sq_head
drivers/nvme/target/core.c:394:27: got unsigned short [unsigned] [usertype] sqhd
prev parent reply other threads:[~2017-09-14 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 20:18 [PATCH] nvmet: implement valid sqhd values in completions James Smart
2017-09-14 17:01 ` Christoph Hellwig [this message]
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=20170914170139.GA25583@infradead.org \
--to=hch@infradead.org \
/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