From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, leonro@nvidia.com, yangx.jy@fujitsu.com,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v6 0/6] RDMA/rxe: Replace mr page map with an xarray
Date: Mon, 23 Jan 2023 15:36:52 -0400 [thread overview]
Message-ID: <Y87h1Cl7aYXDD49M@nvidia.com> (raw)
In-Reply-To: <20230117172540.33205-1-rpearsonhpe@gmail.com>
On Tue, Jan 17, 2023 at 11:25:35AM -0600, Bob Pearson wrote:
> This patch series replaces the page map carried in each memory region
> with a struct xarray. It is based on a sketch developed by Jason
> Gunthorpe. The first five patches are preparation that tries to
> cleanly isolate all the mr specific code into rxe_mr.c. The sixth
> patch is the actual change.
I think this is fine, are all the other people satisfied?
Thanks,
Jason
next prev parent reply other threads:[~2023-01-23 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 17:25 [PATCH for-next v6 0/6] RDMA/rxe: Replace mr page map with an xarray Bob Pearson
2023-01-17 17:25 ` [PATCH for-next v6 1/6] RDMA/rxe: Cleanup mr_check_range Bob Pearson
2023-01-17 17:25 ` [PATCH for-next v6 2/6] RDMA/rxe: Move rxe_map_mr_sg to rxe_mr.c Bob Pearson
2023-01-17 17:25 ` [PATCH for-next v6 3/6] RDMA-rxe: Isolate mr code from atomic_reply() Bob Pearson
2023-01-17 17:25 ` [PATCH for-next v6 4/6] RDMA-rxe: Isolate mr code from atomic_write_reply() Bob Pearson
2023-01-17 17:25 ` [PATCH for-next v6 5/6] RDMA/rxe: Cleanup page variables in rxe_mr.c Bob Pearson
2023-01-17 17:25 ` [PATCH for-next v6 6/6] RDMA/rxe: Replace rxe_map and rxe_phys_buf by xarray Bob Pearson
2023-01-23 19:36 ` Jason Gunthorpe
2023-01-23 19:36 ` Jason Gunthorpe [this message]
2023-01-24 3:43 ` [PATCH for-next v6 0/6] RDMA/rxe: Replace mr page map with an xarray Zhu Yanjun
2023-01-24 5:39 ` Daisuke Matsuda (Fujitsu)
2023-01-24 15:17 ` Jason Gunthorpe
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=Y87h1Cl7aYXDD49M@nvidia.com \
--to=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).