All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jacob Moroni" <jmoroni@google.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH] RDMA/irdma: Fix PBLE_LEVEL_2 FRWR generation
Date: Fri, 16 Oct 2026 18:17:57 +0000	[thread overview]
Message-ID: <sashiko-outbox-174764@kernel.org> (raw)
In-Reply-To: <20261016180901.3292775-1-jmoroni@google.com>

> When an FRWR is posted with only 1 page mapped, it uses a
> direct mapping, with the page-aligned DMA address provided
> in the WQE (reg_addr_pa). This address is obtained by reading
> it from the PBLE that was previously populated during ib_map_mr_sg(),
> but it did not account for whether the original allocation was
> PBLE_LEVEL_1 or PBLE_LEVEL_2 and just assumed it was always level 1.
> 
> As a result, it would program incorrect addresses if the MR was
> originally allocated as PBLE_LEVEL_2.
> 
> Additionally, multi-page PBLE_LEVEL_2 FRWRs were also broken
> because it was using the wrong chunk_size.
> 
> Fix these issues by correctly populating the stag_info fields
> depending on whether it's a PBLE_LEVEL_1 or PBLE_LEVEL_2 MR and
> whether more than 1 page has been mapped or not.
> 
> Tested with NFS over RDMA running various fio scenarios, with
> and without a modified kernel to force it to take the PBLE_LEVEL_2
> path.
> 
> Fixes: 137d264c6f63 ("RDMA/irdma: Add 2 level PBLE support for FMR")
> Suggested-by: Stefan Metzmacher <metze@samba.org>
> Link: https://lore.kernel.org/linux-rdma/20261012161135.494544-1-metze@samba.org/
> Signed-off-by: Jacob Moroni <jmoroni@google.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261016180901.3292775-1-jmoroni@google.com?part=1


      reply	other threads:[~2026-10-16 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 18:09 [PATCH] RDMA/irdma: Fix PBLE_LEVEL_2 FRWR generation Jacob Moroni
2026-10-16 18:17 ` sashiko-bot [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=sashiko-outbox-174764@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=jmoroni@google.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.