linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Devesh Sharma <devesh.sharma@broadcom.com>,
	Doug Ledford <dledford@redhat.com>, <linux-rdma@vger.kernel.org>,
	Naresh Kumar PBS <nareshkumar.pbs@broadcom.com>,
	Selvin Xavier <selvin.xavier@broadcom.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: Re: [PATCH] RDMA/bnxt_re: Use rdma_umem_for_each_dma_block()
Date: Tue, 6 Oct 2020 16:46:19 -0300	[thread overview]
Message-ID: <20201006194619.GA161168@nvidia.com> (raw)
In-Reply-To: <0-v1-b37437a73f35+49c-bnxt_re_dma_block_jgg@nvidia.com>

On Tue, Sep 29, 2020 at 09:24:35PM -0300, Jason Gunthorpe wrote:
> This driver is taking the SGL out of the umem and passing it through a
> struct bnxt_qplib_sg_info. Instead of passing the SGL pass the umem and
> then use rdma_umem_for_each_dma_block() directly.
> 
> Move the calls of ib_umem_num_dma_blocks() closer to their actual point of
> use, npages is only set for non-umem pbl flows.
> 
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> Acked-by: Selvin Xavier <selvin.xavier@broadcom.com>
> Tested-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
>  drivers/infiniband/hw/bnxt_re/ib_verbs.c  | 18 +++-----------
>  drivers/infiniband/hw/bnxt_re/qplib_res.c | 30 +++++++++++++----------
>  drivers/infiniband/hw/bnxt_re/qplib_res.h |  3 +--
>  3 files changed, 22 insertions(+), 29 deletions(-)

Applied to for-next, thanks for checking

Jason

      parent reply	other threads:[~2020-10-06 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  0:24 [PATCH] RDMA/bnxt_re: Use rdma_umem_for_each_dma_block() Jason Gunthorpe
2020-10-06  8:13 ` Selvin Xavier
2020-10-06 19:46 ` 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=20201006194619.GA161168@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=devesh.sharma@broadcom.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=nareshkumar.pbs@broadcom.com \
    --cc=selvin.xavier@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=sriharsha.basavapatna@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;
as well as URLs for NNTP newsgroup(s).