From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe:Support for Host Memory Buffer(HMB)
Date: Mon, 13 Jun 2016 16:46:12 -0400 [thread overview]
Message-ID: <20160613204611.GF12766@localhost.localdomain> (raw)
In-Reply-To: <1465565964-7167-1-git-send-email-a.dawn@samsung.com>
On Fri, Jun 10, 2016@07:09:24PM +0530, Arnav Dawn wrote:
> +
> +struct hmb_descriptor {
> + __u64 badd;
> + __u32 bsize;
Based on your usage, these types should be "le64" and "le32"?
> +struct hmb_info {
> + /* Array of unalligned HMB Discriptor info */
> + struct hmb_descriptor_info *hmb_desc_info;
> + /* count of entries in the list */
> + u32 hmb_desc_info_list_count;
> +
> + /* HMB descriptor Info list */
> + struct hmb_descriptor_info hmb_desc_info_list;
> +
> + /* preferred HMB size set by device */
> + u64 host_mem_pre;
> +
> + /* min HMB size set by device */
> + u64 host_mem_min;
> +
> + /* HMB flags MR,ENABLE */
> + u8 flags;
> +};
Please use kernel-doc style if you're going to comment your structure.
> diff --git a/include/linux/nvme.h b/include/linux/nvme.h
> index 7d51b29..c29f514 100644
> --- a/include/linux/nvme.h
> +++ b/include/linux/nvme.h
> @@ -119,7 +119,10 @@ struct nvme_id_ctrl {
> __u8 apsta;
> __le16 wctemp;
> __le16 cctemp;
> - __u8 rsvd270[242];
> + __u8 rsvd270[2];
> + __u32 hmpre;
> + __u32 hmmin;
These should also be le32 types.
next prev parent reply other threads:[~2016-06-13 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 13:39 [PATCH] NVMe:Support for Host Memory Buffer(HMB) Arnav Dawn
2016-06-13 20:46 ` Keith Busch [this message]
2016-06-13 22:08 ` Keith Busch
2016-06-15 10:48 ` 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=20160613204611.GF12766@localhost.localdomain \
--to=keith.busch@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