[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 11 Nov 2022 06:13:06 +0000
From: "lizhijian@...itsu.com" <lizhijian@...itsu.com>
To: Zhu Yanjun <zyjzyj2000@...il.com>, Jason Gunthorpe <jgg@...pe.ca>,
Leon Romanovsky <leon@...nel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"yangx.jy@...itsu.com" <yangx.jy@...itsu.com>
Subject: Re: [for-next PATCH 0/5] iova_to_vaddr refactor
CC+ Xiao
On 11/11/2022 12:30, Li Zhijian wrote:
> Background:
> iova_to_addr just lookups at the map which is constructed and manages the
> relationship between iova to vaddr when MR is registering. By conventional,
> we should map the userspace address(iova) every time we want to access it.
> Please refer to the previous discussion[1][2] for more details.
>
> Refactor:
> In this refactoring, we will do the map every time before the user really
> accesses it.
>
> patch1,3,5 are cleanup and preparation.
> patch2 is to make all subroutines accessing the iova use iova_to_vaddr() API.
> patch4 is the refactor.
>
> [1]: https://www.spinics.net/lists/linux-rdma/msg113206.html
> [2]: https://lore.kernel.org/all/20220118123505.GF84788@nvidia.com/
>
> Li Zhijian (5):
> RDMA/rxe: Remove rxe_phys_buf.size
> RDMA/rxe: use iova_to_vaddr to transform iova for rxe_mr_copy
> RDMA/rxe: iova_to_vaddr cleanup
> RDMA/rxe: refactor iova_to_vaddr
> RDMA/rxe: Rename iova_to_vaddr to rxe_map_iova
>
> drivers/infiniband/sw/rxe/rxe_loc.h | 3 +-
> drivers/infiniband/sw/rxe/rxe_mr.c | 128 +++++++++++---------------
> drivers/infiniband/sw/rxe/rxe_resp.c | 5 +-
> drivers/infiniband/sw/rxe/rxe_verbs.c | 1 -
> drivers/infiniband/sw/rxe/rxe_verbs.h | 6 +-
> 5 files changed, 62 insertions(+), 81 deletions(-)
>
Powered by blists - more mailing lists