public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
	andrew.gospodarek@broadcom.com,
	Saravanan Vajravel <saravanan.vajravel@broadcom.com>
Subject: Re: [PATCH for-next v2 1/1] RDMA/bnxt_re: Add support for dmabuf pinned memory regions
Date: Tue, 15 Aug 2023 15:58:38 -0300	[thread overview]
Message-ID: <ZNvK3m+FqoD0t+vj@nvidia.com> (raw)
In-Reply-To: <1690790473-25850-2-git-send-email-selvin.xavier@broadcom.com>

On Mon, Jul 31, 2023 at 01:01:13AM -0700, Selvin Xavier wrote:
> From: Saravanan Vajravel <saravanan.vajravel@broadcom.com>
> 
> Support the new verb which indicates dmabuf support.
> bnxt doesn't support ODP. So use the pinned version of the
> dmabuf APIs to enable bnxt_re devices to work as dmabuf importer.
> 
> Signed-off-by: Saravanan Vajravel <saravanan.vajravel@broadcom.com>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
>  drivers/infiniband/hw/bnxt_re/ib_verbs.c | 83 ++++++++++++++++++++++----------
>  drivers/infiniband/hw/bnxt_re/ib_verbs.h |  4 ++
>  drivers/infiniband/hw/bnxt_re/main.c     |  1 +
>  3 files changed, 62 insertions(+), 26 deletions(-)

Applied to for-next, thanks

Jason

      reply	other threads:[~2023-08-15 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  8:01 [PATCH for-next v2 0/1] RDMA/bnxt_re: Add dmabuf support Selvin Xavier
2023-07-31  8:01 ` [PATCH for-next v2 1/1] RDMA/bnxt_re: Add support for dmabuf pinned memory regions Selvin Xavier
2023-08-15 18:58   ` Jason Gunthorpe [this message]

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=ZNvK3m+FqoD0t+vj@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=saravanan.vajravel@broadcom.com \
    --cc=selvin.xavier@broadcom.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