linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Michal Kalderon <michal.kalderon@marvell.com>
Cc: ariel.elior@marvell.com, dledford@redhat.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next] RDMA/qedr: Add kernel capability flags for dpm enabled mode
Date: Wed, 20 Nov 2019 12:53:01 -0400	[thread overview]
Message-ID: <20191120165301.GI22515@ziepe.ca> (raw)
In-Reply-To: <20191120132009.14107-1-michal.kalderon@marvell.com>

On Wed, Nov 20, 2019 at 03:20:09PM +0200, Michal Kalderon wrote:
> diff --git a/include/uapi/rdma/qedr-abi.h b/include/uapi/rdma/qedr-abi.h
> index c022ee26089b..a0b83c9d4498 100644
> +++ b/include/uapi/rdma/qedr-abi.h
> @@ -48,6 +48,18 @@ struct qedr_alloc_ucontext_req {
>  	__u32 reserved;
>  };
>  
> +#define QEDR_LDPM_MAX_SIZE	(8192)
> +#define QEDR_EDPM_TRANS_SIZE	(64)
> +
> +enum qedr_rdma_dpm_type {
> +	QEDR_DPM_TYPE_NONE		= 0,
> +	QEDR_DPM_TYPE_ROCE_ENHANCED	= 1 << 0,
> +	QEDR_DPM_TYPE_ROCE_LEGACY	= 1 << 1,
> +	QEDR_DPM_TYPE_IWARP_LEGACY	= 1 << 2,
> +	QEDR_DPM_TYPE_RESERVED		= 1 << 3,
> +	QEDR_DPM_SIZES_SET		= 1 << 4,
> +};
> +
>  struct qedr_alloc_ucontext_resp {
>  	__aligned_u64 db_pa;
>  	__u32 db_size;
> @@ -59,10 +71,12 @@ struct qedr_alloc_ucontext_resp {
>  	__u32 sges_per_recv_wr;
>  	__u32 sges_per_srq_wr;
>  	__u32 max_cqes;
> -	__u8 dpm_enabled;
> +	__u8 dpm_flags;

Is this redefinition backwards compatible with old user space?
That should be described in the commit message

Jason

  reply	other threads:[~2019-11-20 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 13:20 [PATCH rdma-next] RDMA/qedr: Add kernel capability flags for dpm enabled mode Michal Kalderon
2019-11-20 16:53 ` Jason Gunthorpe [this message]
2019-11-21  8:12   ` [EXT] " Michal Kalderon

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=20191120165301.GI22515@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=ariel.elior@marvell.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michal.kalderon@marvell.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).