mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Leon Romanovsky <leon@kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
Subject: Re: [for-next PATCH 0/5] iova_to_vaddr refactor
Date: Fri, 11 Nov 2022 06:13:06 +0000	[thread overview]
Message-ID: <a7decec2-77d9-db4c-ff66-ff597da8bc71@fujitsu.com> (raw)
In-Reply-To: <1668141030-2-1-git-send-email-lizhijian@fujitsu.com>

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(-)
> 

      parent reply	other threads:[~2022-11-11  6:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  4:30 Li Zhijian
2022-11-11  4:30 ` [for-next PATCH 1/5] RDMA/rxe: Remove rxe_phys_buf.size Li Zhijian
2022-11-18 16:38   ` Jason Gunthorpe
2022-11-11  4:30 ` [for-next PATCH 2/5] RDMA/rxe: use iova_to_vaddr to transform iova for rxe_mr_copy Li Zhijian
2022-11-18 16:41   ` Jason Gunthorpe
2022-11-11  4:30 ` [for-next PATCH 3/5] RDMA/rxe: iova_to_vaddr cleanup Li Zhijian
2022-11-11  4:30 ` [for-next PATCH 4/5] RDMA/rxe: refactor iova_to_vaddr Li Zhijian
2022-11-16 12:37   ` Fabio M. De Francesco
2022-11-18  1:32     ` lizhijian
2022-11-21 18:53     ` Jason Gunthorpe
2022-11-22 23:24       ` Fabio M. De Francesco
2022-11-22 23:55         ` Fabio M. De Francesco
2022-11-16 12:49   ` Fabio M. De Francesco
2022-11-18 17:33   ` Jason Gunthorpe
2022-11-11  4:32 ` [for-next PATCH 5/5] RDMA/rxe: Rename iova_to_vaddr to rxe_map_iova Li Zhijian
2022-11-11  6:13 ` lizhijian [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=a7decec2-77d9-db4c-ff66-ff597da8bc71@fujitsu.com \
    --to=lizhijian@fujitsu.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yangx.jy@fujitsu.com \
    --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

all inboxes | Powered by JetHome®