linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Yixian Liu <liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 for-next 1/4] RDMA/hns: Support rq record doorbell for the user space
Date: Fri, 9 Feb 2018 08:23:53 -0700	[thread overview]
Message-ID: <20180209152353.GC7570@ziepe.ca> (raw)
In-Reply-To: <1518176700-126906-2-git-send-email-liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

On Fri, Feb 09, 2018 at 07:44:57PM +0800, Yixian Liu wrote:

> diff --git a/drivers/infiniband/hw/hns/hns_roce_device.h b/drivers/infiniband/hw/hns/hns_roce_device.h
> index 42c3b5a..2da30fc 100644
> +++ b/drivers/infiniband/hw/hns/hns_roce_device.h
> @@ -105,6 +105,10 @@
>  #define PAGES_SHIFT_24				24
>  #define PAGES_SHIFT_32				32
>  
> +enum {
> +	HNS_ROCE_SUPPORT_RQ_RECORD_DB = BIT(0),
> +};

This belongs in the uapi header same remark in userspace. Dont' use
BIT in uapi headers.

Same remark for the other cap_flags in other patches

> diff --git a/include/uapi/rdma/hns-abi.h b/include/uapi/rdma/hns-abi.h
> index 5d74019..1b05d00 100644
> +++ b/include/uapi/rdma/hns-abi.h
> @@ -48,6 +48,10 @@ struct hns_roce_ib_create_qp {
>  	__u8    reserved[5];
>  };
>  
> +struct hns_roce_ib_create_qp_resp {
> +	__u32	cap_flags;
> +};
> +
>  struct hns_roce_ib_alloc_ucontext_resp {
>  	__u32	qp_tab_size;
>  };

All structures in this file need to be aligned to 64 bits, add the
implicit padding necessary.

Jasn
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-02-09 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 11:44 [PATCH v2 for-next 0/4] Support rq and cq record doorbell Yixian Liu
     [not found] ` <1518176700-126906-1-git-send-email-liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-02-09 11:44   ` [PATCH v2 for-next 1/4] RDMA/hns: Support rq record doorbell for the user space Yixian Liu
     [not found]     ` <1518176700-126906-2-git-send-email-liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-02-09 15:23       ` Jason Gunthorpe [this message]
     [not found]         ` <20180209152353.GC7570-uk2M96/98Pc@public.gmane.org>
2018-02-11  5:44           ` Liuyixian (Eason)
2018-02-09 11:44   ` [PATCH v2 for-next 2/4] RDMA/hns: Support cq " Yixian Liu
2018-02-09 11:44   ` [PATCH v2 for-next 3/4] RDMA/hns: Support rq record doorbell for kernel space Yixian Liu
2018-02-09 11:45   ` [PATCH v2 for-next 4/4] RDMA/hns: Support cq " Yixian Liu

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=20180209152353.GC7570@ziepe.ca \
    --to=jgg-uk2m96/98pc@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).