From: Daisuke Matsuda <dskmtsd@gmail.com>
To: linux-rdma@vger.kernel.org, leon@kernel.org, jgg@ziepe.ca,
zyjzyj2000@gmail.com
Subject: Re: [PATCH for-next v1] RDMA/rxe: Remove redundant page presence check
Date: Sun, 8 Jun 2025 18:51:16 +0900 [thread overview]
Message-ID: <8a09c0e9-a25b-447c-b201-1b4b40674b99@gmail.com> (raw)
In-Reply-To: <20250608093723.3132-1-dskmtsd@gmail.com>
Sorry, I mistakenly sent an intermediate work. Please ignore this one and see v2.
On 2025/06/08 18:37, Daisuke Matsuda wrote:
> hmm_pfn_to_page() does not return NULL. ib_umem_odp_map_dma_and_lock()
> should return an error in case the target pages cannot be mapped until
> timeout, so these checks can safely be removed.
>
> Signed-off-by: Daisuke Matsuda <dskmtsd@gmail.com>
> ---
> drivers/infiniband/sw/rxe/rxe_odp.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_odp.c b/drivers/infiniband/sw/rxe/rxe_odp.c
> index dbc5a5600eb7..fb88f2901c58 100644
> --- a/drivers/infiniband/sw/rxe/rxe_odp.c
> +++ b/drivers/infiniband/sw/rxe/rxe_odp.c
> @@ -203,8 +203,6 @@ static int __rxe_odp_mr_copy(struct rxe_mr *mr, u64 iova, void *addr,
>
> page = hmm_pfn_to_page(umem_odp->map.pfn_list[idx]);
> user_va = kmap_local_page(page);
> - if (!user_va)
> - return -EFAULT;
>
> src = (dir == RXE_TO_MR_OBJ) ? addr : user_va;
> dest = (dir == RXE_TO_MR_OBJ) ? user_va : addr;
> @@ -286,8 +284,6 @@ static enum resp_states rxe_odp_do_atomic_op(struct rxe_mr *mr, u64 iova,
> idx = rxe_odp_iova_to_index(umem_odp, iova);
> page_offset = rxe_odp_iova_to_page_offset(umem_odp, iova);
> page = hmm_pfn_to_page(umem_odp->map.pfn_list[idx]);
> - if (!page)
> - return RESPST_ERR_RKEY_VIOLATION;
>
> if (unlikely(page_offset & 0x7)) {
> rxe_dbg_mr(mr, "iova not aligned\n");
prev parent reply other threads:[~2025-06-08 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 9:37 [PATCH for-next v1] RDMA/rxe: Remove redundant page presence check Daisuke Matsuda
2025-06-08 9:51 ` Daisuke Matsuda [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=8a09c0e9-a25b-447c-b201-1b4b40674b99@gmail.com \
--to=dskmtsd@gmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zyjzyj2000@gmail.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