All of lore.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,
	Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
	Kashyap Desai <kashyap.desai@broadcom.com>
Subject: Re: [PATCH for-rc] RDMA/bnxt_re: Fix the page_size used during the MR creation
Date: Fri, 12 May 2023 18:32:58 -0300	[thread overview]
Message-ID: <ZF6wilKJPBM9vBbr@nvidia.com> (raw)
In-Reply-To: <1683484169-9539-1-git-send-email-selvin.xavier@broadcom.com>

On Sun, May 07, 2023 at 11:29:29AM -0700, Selvin Xavier wrote:
> Driver populates the list of pages used for Memory region wrongly when
> page size is more than system page size. This is causing a failure
> when some of the applications that creates MR with page size as 2M.
> Since HW can support multiple page sizes, pass the correct page size
> while creating the MR.
> 
> Also, driver need not adjust the number of pages when HW Queues
> are created with user memory. It should work with the number of
> dma blocks returned by ib_umem_num_dma_blocks. Fix this calculation also.
> 
> Fixes: 0c4dcd602817 ("RDMA/bnxt_re: Refactor hardware queue memory allocation")
> Fixes: f6919d56388c ("RDMA/bnxt_re: Code refactor while populating user MRs")
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Signed-off-by: Kashyap Desai <kashyap.desai@broadcom.com>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
>  drivers/infiniband/hw/bnxt_re/qplib_res.c | 12 ++----------
>  drivers/infiniband/hw/bnxt_re/qplib_sp.c  |  7 +++----
>  2 files changed, 5 insertions(+), 14 deletions(-)

Applied to for-rc, thanks

Jason

      reply	other threads:[~2023-05-12 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07 18:29 [PATCH for-rc] RDMA/bnxt_re: Fix the page_size used during the MR creation Selvin Xavier
2023-05-12 21:32 ` 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=ZF6wilKJPBM9vBbr@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=kashyap.desai@broadcom.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.