From: Sagi Grimberg <sagi@lightbits.io>
To: Christoph Hellwig <hch@lst.de>, axboe@kernel.dk, keith.busch@intel.com
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jay Freyensee <james.p.freyensee@intel.com>,
Ming Lin <ming.l@ssi.samsung.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 3/5] nvme-rdma.h: Add includes for nvme rdma_cm negotiation
Date: Tue, 7 Jun 2016 14:59:58 +0300 [thread overview]
Message-ID: <5756B73E.4050907@lightbits.io> (raw)
In-Reply-To: <1465248215-18186-4-git-send-email-hch@lst.de>
We forgot to CC Linux-rdma, CC'ing...
On 07/06/16 00:23, Christoph Hellwig wrote:
> From: Sagi Grimberg <sagi@grimberg.me>
>
> NVMe over Fabrics RDMA transport defines a connection establishment
> protocol over the RDMA connection manager. This header will be used by
> both the host and target drivers to negotiate the connection
> establishment parameters.
>
> Signed-off-by: Jay Freyensee <james.p.freyensee@intel.com>
> Signed-off-by: Ming Lin <ming.l@ssi.samsung.com>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> include/linux/nvme-rdma.h | 71 +++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 71 insertions(+)
> create mode 100644 include/linux/nvme-rdma.h
>
> diff --git a/include/linux/nvme-rdma.h b/include/linux/nvme-rdma.h
> new file mode 100644
> index 0000000..bf240a3
> --- /dev/null
> +++ b/include/linux/nvme-rdma.h
> @@ -0,0 +1,71 @@
> +/*
> + * Copyright (c) 2015 Mellanox Technologies. All rights reserved.
> + *
> + * This program is free software; you can redistribute it and/or modify it
> + * under the terms and conditions of the GNU General Public License,
> + * version 2, as published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope it will be useful, but WITHOUT
> + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
> + * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
> + * more details.
> + */
> +
> +#ifndef _LINUX_NVME_RDMA_H
> +#define _LINUX_NVME_RDMA_H
> +
> +enum nvme_rdma_cm_fmt {
> + NVME_RDMA_CM_FMT_1_0 = 0x0,
> +};
> +
> +enum nvme_rdma_cm_status {
> + NVME_RDMA_CM_INVALID_LEN = 0x01,
> + NVME_RDMA_CM_INVALID_RECFMT = 0x02,
> + NVME_RDMA_CM_INVALID_QID = 0x03,
> + NVME_RDMA_CM_INVALID_HSQSIZE = 0x04,
> + NVME_RDMA_CM_INVALID_HRQSIZE = 0x05,
> + NVME_RDMA_CM_NO_RSC = 0x06,
> + NVME_RDMA_CM_INVALID_IRD = 0x07,
> + NVME_RDMA_CM_INVALID_ORD = 0x08,
> +};
> +
> +/**
> + * struct nvme_rdma_cm_req - rdma connect request
> + *
> + * @recfmt: format of the RDMA Private Data
> + * @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
> + */
> +struct nvme_rdma_cm_req {
> + __le16 recfmt;
> + __le16 qid;
> + __le16 hrqsize;
> + __le16 hsqsize;
> + u8 rsvd[24];
> +};
> +
> +/**
> + * struct nvme_rdma_cm_rep - rdma connect reply
> + *
> + * @recfmt: format of the RDMA Private Data
> + * @crqsize: controller receive queue size
> + */
> +struct nvme_rdma_cm_rep {
> + __le16 recfmt;
> + __le16 crqsize;
> + u8 rsvd[28];
> +};
> +
> +/**
> + * struct nvme_rdma_cm_rej - rdma connect reject
> + *
> + * @recfmt: format of the RDMA Private Data
> + * @fsts: error status for the associated connect request
> + */
> +struct nvme_rdma_cm_rej {
> + __le16 recfmt;
> + __le16 sts;
> +};
> +
> +#endif /* _LINUX_NVME_RDMA_H */
>
next prev parent reply other threads:[~2016-06-07 12:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 21:23 NVMe over Fabrics RDMA transport drivers Christoph Hellwig
2016-06-06 21:23 ` [PATCH 1/5] blk-mq: Introduce blk_mq_reinit_tagset Christoph Hellwig
2016-06-06 21:23 ` [PATCH 2/5] nvme: add new reconnecting controller state Christoph Hellwig
2016-06-06 21:23 ` [PATCH 3/5] nvme-rdma.h: Add includes for nvme rdma_cm negotiation Christoph Hellwig
2016-06-07 11:59 ` Sagi Grimberg [this message]
2016-06-06 21:23 ` [PATCH 4/5] nvmet-rdma: add a NVMe over Fabrics RDMA target driver Christoph Hellwig
2016-06-07 12:00 ` Sagi Grimberg
2016-06-09 21:42 ` Steve Wise
2016-06-09 21:54 ` Ming Lin
2016-06-14 14:32 ` Christoph Hellwig
2016-06-09 23:03 ` Steve Wise
2016-06-14 14:31 ` Christoph Hellwig
2016-06-14 15:14 ` Steve Wise
[not found] ` <00ea01d1c64f$64db8880$2e929980$@opengridcomputing.com>
2016-06-14 15:23 ` Steve Wise
2016-06-14 16:10 ` Steve Wise
2016-06-14 16:22 ` Steve Wise
2016-06-15 18:32 ` Sagi Grimberg
2016-06-14 16:47 ` Hefty, Sean
2016-06-06 21:23 ` [PATCH 5/5] nvme-rdma: add a NVMe over Fabrics RDMA host driver Christoph Hellwig
2016-06-07 12:00 ` Sagi Grimberg
2016-06-07 14:47 ` Keith Busch
2016-06-07 15:15 ` Freyensee, James P
2016-06-07 11:57 ` NVMe over Fabrics RDMA transport drivers Sagi Grimberg
2016-06-07 12:01 ` Christoph Hellwig
2016-06-07 14:55 ` Woodruff, Robert J
2016-06-07 20:14 ` Steve Wise
2016-06-07 20:27 ` Christoph Hellwig
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=5756B73E.4050907@lightbits.io \
--to=sagi@lightbits.io \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=james.p.freyensee@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ming.l@ssi.samsung.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).