From: Jason Gunthorpe <jgg@ziepe.ca>
To: Krishnamraju Eraparaju <krishna2@chelsio.com>
Cc: sagi@grimberg.me, linux-rdma@vger.kernel.org, bharat@chelsio.com,
nirranjan@chelsio.com, linux-nvme@lists.infradead.org,
hch@lst.de
Subject: Re: [PATCH for-rc] nvme-rdma/nvmet-rdma: Allocate sufficient RW ctxs to match hosts pgs len
Date: Wed, 26 Feb 2020 13:07:20 -0400 [thread overview]
Message-ID: <20200226170720.GY31668@ziepe.ca> (raw)
In-Reply-To: <20200226141318.28519-1-krishna2@chelsio.com>
On Wed, Feb 26, 2020 at 07:43:18PM +0530, Krishnamraju Eraparaju wrote:
> diff --git a/include/linux/nvme-rdma.h b/include/linux/nvme-rdma.h
> index 3ec8e50efa16..2d6f2cf1e319 100644
> +++ b/include/linux/nvme-rdma.h
> @@ -52,13 +52,15 @@ static inline const char *nvme_rdma_cm_msg(enum nvme_rdma_cm_status status)
> * @qid: queue Identifier for the Admin or I/O Queue
> * @hrqsize: host receive queue size to be created
> * @hsqsize: host send queue size to be created
> + * @hmax_fr_pages: host maximum pages per fast reg
> */
> struct nvme_rdma_cm_req {
> __le16 recfmt;
> __le16 qid;
> __le16 hrqsize;
> __le16 hsqsize;
> - u8 rsvd[24];
> + __le32 hmax_fr_pages;
> + u8 rsvd[20];
> };
This is an on the wire change - do you need to get approval from some
standards body?
Jason
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-02-26 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 14:13 [PATCH for-rc] nvme-rdma/nvmet-rdma: Allocate sufficient RW ctxs to match hosts pgs len Krishnamraju Eraparaju
2020-02-26 17:07 ` Jason Gunthorpe [this message]
2020-02-26 23:19 ` Sagi Grimberg
2020-02-26 23:05 ` Sagi Grimberg
2020-02-27 15:46 ` Krishnamraju Eraparaju
2020-02-27 23:14 ` Sagi Grimberg
2020-03-01 14:05 ` Max Gurtovoy
2020-03-02 7:32 ` Krishnamraju Eraparaju
2020-03-02 17:43 ` Sagi Grimberg
2020-03-03 23:11 ` Max Gurtovoy
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=20200226170720.GY31668@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bharat@chelsio.com \
--cc=hch@lst.de \
--cc=krishna2@chelsio.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=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