All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Shiraz Saleem <shiraz.saleem@intel.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2 for-rc 0/3] Fixes for 64K page size support
Date: Mon, 4 Dec 2023 19:54:49 -0400	[thread overview]
Message-ID: <20231204235449.GA2767549@nvidia.com> (raw)
In-Reply-To: <20231129202143.1434-1-shiraz.saleem@intel.com>

On Wed, Nov 29, 2023 at 02:21:40PM -0600, Shiraz Saleem wrote:
> This is a three patch series.
> 
> The first core hunk corrects the core iterator to use __sg_advance to skip
> preceding 4k HCA pages.
> 
> The second patch corrects an iWarp issue where the SQ must be PAGE_SIZE
> aligned.
> 
> The third patch corrects an issue with the RDMA driver use of
> ib_umem_find_best_pgsz(). QP and CQ allocations pass PAGE_SIZE as the
> only bitmap bit. This is incorrect and should use the precise 4k value.
> 
> v1->v2: Add a umem specific block iter next function
> 
> Mike Marciniszyn (3):
>   RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz
>   RDMA/irdma: Ensure iWarp QP queue memory is OS paged aligned
>   RDMA/irdma: Fix support for 64k pages

Applied to for-rc, thanks

Jason

      parent reply	other threads:[~2023-12-04 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 20:21 [PATCH v2 for-rc 0/3] Fixes for 64K page size support Shiraz Saleem
2023-11-29 20:21 ` [PATCH v2 for-rc 1/3] RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz Shiraz Saleem
2023-11-29 20:40   ` Jason Gunthorpe
2023-11-29 20:21 ` [PATCH v2 for-rc 2/3] RDMA/irdma: Ensure iWarp QP queue memory is OS paged aligned Shiraz Saleem
2023-11-29 20:21 ` [PATCH v2 for-rc 3/3] RDMA/irdma: Fix support for 64k pages Shiraz Saleem
2023-12-04 23:54 ` 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=20231204235449.GA2767549@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=shiraz.saleem@intel.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.