From: Jason Gunthorpe <jgg@nvidia.com>
To: Weihang Li <liweihang@huawei.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org, linuxarm@openeuler.org
Subject: Re: [PATCH RFC v2 rdma-core 5/6] libhns: Add direct verb to support config DCA memory pool
Date: Fri, 12 Mar 2021 10:27:47 -0400 [thread overview]
Message-ID: <20210312142747.GB2356281@nvidia.com> (raw)
In-Reply-To: <1614847759-33139-6-git-send-email-liweihang@huawei.com>
On Thu, Mar 04, 2021 at 04:49:18PM +0800, Weihang Li wrote:
> diff --git a/libibverbs/verbs.h b/libibverbs/verbs.h
> index 656b0f9..db37dce 100644
> +++ b/libibverbs/verbs.h
> @@ -918,6 +918,7 @@ enum ibv_qp_create_flags {
> IBV_QP_CREATE_CVLAN_STRIPPING = 1 << 9,
> IBV_QP_CREATE_SOURCE_QPN = 1 << 10,
> IBV_QP_CREATE_PCI_WRITE_END_PADDING = 1 << 11,
> + IBV_QP_CREATE_DYNAMIC_CONTEXT_ATTACH = 1 << 13,
> };
No, all the stuff related to these kinds of extensions must be in the
hnsdv.h and can't be used with the normal APIs at all
Jason
next prev parent reply other threads:[~2021-03-12 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 8:49 [PATCH RFC v2 rdma-core 0/6] libhns: Add support for Dynamic Context Attachment Weihang Li
2021-03-04 8:49 ` [PATCH RFC v2 rdma-core 1/6] Update kernel headers Weihang Li
2021-03-04 8:49 ` [PATCH RFC v2 rdma-core 2/6] libhns: Introduce DCA for RC QP Weihang Li
2021-03-04 8:49 ` [PATCH RFC v2 rdma-core 3/6] libhns: Add support for shrinking DCA memory pool Weihang Li
2021-03-04 8:49 ` [PATCH RFC v2 rdma-core 4/6] libhns: Add support for attaching QP's WQE buffer Weihang Li
2021-03-04 8:49 ` [PATCH RFC v2 rdma-core 5/6] libhns: Add direct verb to support config DCA memory pool Weihang Li
2021-03-12 14:27 ` Jason Gunthorpe [this message]
2021-03-15 3:21 ` liweihang
2021-03-04 8:49 ` [PATCH RFC v2 rdma-core 6/6] libhns: Add man pages to introduce DCA feature Weihang Li
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=20210312142747.GB2356281@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=liweihang@huawei.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